CVE-2012-5524 json
The _ssl_verify_callback function in tls_nb.py in Gajim before 0.15.3 does not properly verify SSL certificates, which allows remote attack…
published 2014-02-08 12 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5416
- 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 67%
- public exploits
- 0
- none known
Summary
The _ssl_verify_callback function in tls_nb.py in Gajim before 0.15.3 does not properly verify SSL certificates, which allows remote attackers to conduct man-in-the-middle (MITM) attacks and spoof servers via an arbitrary certificate from a trusted CA.
Patch / fix
- gajim Debian 14, Debian 13, Debian 12 0.15.4-1
debian advisories DEBIAN-CVE-2012-5524
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-5524 updated cvss 4.3
gajim: Improper handling of invalid certificates
-
Red Hat All currently supported Red Hat productsnot 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.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- trac.gajim.org https://trac.gajim.org/ticket/7252 referenced PoC, tagged "exploit" by a source, unverified
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-20 Improper Input Validation
References
-
trac.gajim.org
/ticket/7252
exploit, patch
-
security.gentoo.org
/glsa/glsa-201401-02.xml
vendor-advisory
-
openwall.com
/lists/oss-security/2012/11/11/6
mailing-list
- trac.gajim.org /query?status=closed&group=resolution&milestone=0.15.3
Sources
- CVE List CVE-2012-5524
- NVD CVE-2012-5524
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.