CVE-2012-5524
Last modified
CVE-2012-5524 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.15% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Gajim | Gajim | <= 0.15.2 |
| Gajim | Gajim | 0.1 |
| Gajim | Gajim | 0.2 |
| Gajim | Gajim | 0.2.1 |
| Gajim | Gajim | 0.3 |
| Gajim | Gajim | 0.4 |
| Gajim | Gajim | 0.4.1 |
| Gajim | Gajim | 0.5 |
| Gajim | Gajim | 0.5.1 |
| Gajim | Gajim | 0.6 |
| Gajim | Gajim | 0.6.1 |
| Gajim | Gajim | 0.7 |
| Gajim | Gajim | 0.7.1 |
| Gajim | Gajim | 0.8 |
| Gajim | Gajim | 0.8.1 |
| Gajim | Gajim | 0.8.2 |
| Gajim | Gajim | 0.9 |
| Gajim | Gajim | 0.9.1 |
| Gajim | Gajim | 0.10 |
| Gajim | Gajim | 0.10.1 |
| Gajim | Gajim | 0.11 |
| Gajim | Gajim | 0.11.1 |
| Gajim | Gajim | 0.11.2 |
| Gajim | Gajim | 0.11.3 |
| Gajim | Gajim | 0.11.4 |
| Gajim | Gajim | 0.12 |
| Gajim | Gajim | 0.12.1 |
| Gajim | Gajim | 0.12.2 |
| Gajim | Gajim | 0.12.3 |
| Gajim | Gajim | 0.12.4 |
| Gajim | Gajim | 0.12.5 |
| Gajim | Gajim | 0.13 |
| Gajim | Gajim | 0.13.1 |
| Gajim | Gajim | 0.13.2 |
| Gajim | Gajim | 0.13.3 |
| Gajim | Gajim | 0.13.4 |
| Gajim | Gajim | 0.14 |
| Gajim | Gajim | 0.14.1 |
| Gajim | Gajim | 0.14.2 |
| Gajim | Gajim | 0.14.3 |
| Gajim | Gajim | 0.14.4 |
| Gajim | Gajim | 0.15 |
| Gajim | Gajim | 0.15.1 |
References
- https://trac.gajim.org/ticket/7252Exploit, Patch
- https://trac.gajim.org/ticket/7252Exploit, Patch
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2012-5524?
How severe is CVE-2012-5524?
How do I fix CVE-2012-5524?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2012
- CVE-2012-5518vdsm: certificate generation upon node creation allowing vds…7.5
- CVE-2012-5519CUPS 1.4.4, when running in certain Linux distributions such…
- CVE-2012-5520The send_to_sourcefire function in manage_sql.c in OpenVAS M…
- CVE-2012-5521quagga (ospf6d) 0.99.21 has a DoS flaw in the way the ospf6d…6.5
- CVE-2012-5522MantisBT before 1.2.12 does not use an expected default valu…
- CVE-2012-5523core/email_api.php in MantisBT before 1.2.12 does not proper…
- CVE-2012-5525The get_page_from_gfn hypercall function in Xen 4.2 allows l…
- CVE-2012-5526CGI.pm module before 3.63 for Perl does not properly escape …
- CVE-2012-5527Claws Mail vCalendar plugin: credentials exposed on interfac…5.5
- CVE-2012-5528Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2012-5529TraceManager in Firebird 2.5.0 and 2.5.1, when trace is enab…
- CVE-2012-5530The (1) pcmd and (2) pmlogger init scripts in Performance Co…
Are you affected by CVE-2012-5524?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST