CVE-2013-4488 json
libgadu before 1.12.0 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers.
published 12y ago modified 4mo ago also EUVD-2013-4353
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
libgadu before 1.12.0 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers.
Is CVE-2013-4488 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-4488 updated cvss 5.8
libgadu: missing ssl certificate validation
-
Red Hat Enterprise Linux 7 libgadunot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
security.gentoo.org
/glsa/201508-02
vendor-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2014:185
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2013-December/125143.html
vendor-advisory
- bugzilla.redhat.com /show_bug.cgi?id=1025718
-
securityfocus.com
/bid/63473
vdb-entry
-
openwall.com
/lists/oss-security/2013/10/31/5
mailing-list
-
mail-archive.com
/libgadu-devel%40lists.ziew.org/msg01017.html
mailing-list
Sources
- CVE List CVE-2013-4488
- NVD CVE-2013-4488
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.