CVE-2013-6169
UnknownEPSS 1.59%
Last modified
CVE-2013-6169 is a vulnerability of currently unknown severity. The TLS driver in ejabberd before 2.1.12 supports (1) SSLv2 and (2) weak SSL ciphers, which makes it easier for remote attackers to obtain sensitive information via a brute-force attack.. EPSS estimates a 1.59% chance of exploitation in the next 30 days.
Description
The TLS driver in ejabberd before 2.1.12 supports (1) SSLv2 and (2) weak SSL ciphers, which makes it easier for remote attackers to obtain sensitive information via a brute-force attack.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Process-One | Ejabberd | <= 2.1.12 |
| Process-One | Ejabberd | 0.9 |
| Process-One | Ejabberd | 0.9.1 |
| Process-One | Ejabberd | 0.9.8 |
| Process-One | Ejabberd | 1.0.0 |
| Process-One | Ejabberd | 1.1.0 |
| Process-One | Ejabberd | 1.1.1 |
| Process-One | Ejabberd | 1.1.1.0 |
| Process-One | Ejabberd | 1.1.1.1 |
| Process-One | Ejabberd | 1.1.2 |
| Process-One | Ejabberd | 1.1.3 |
| Process-One | Ejabberd | 1.1.14 |
| Process-One | Ejabberd | 2.0.0 |
| Process-One | Ejabberd | 2.0.1_2 |
| Process-One | Ejabberd | 2.0.2 |
| Process-One | Ejabberd | 2.0.3 |
| Process-One | Ejabberd | 2.0.4 |
| Process-One | Ejabberd | 2.0.5 |
| Process-One | Ejabberd | 2.1.0 |
| Process-One | Ejabberd | 2.1.1 |
| Process-One | Ejabberd | 2.1.2 |
| Process-One | Ejabberd | 2.1.3 |
| Process-One | Ejabberd | 2.1.4 |
| Process-One | Ejabberd | 2.1.5 |
| Process-One | Ejabberd | 2.1.6 |
| Process-One | Ejabberd | 2.1.7 |
| Process-One | Ejabberd | 2.1.8 |
| Process-One | Ejabberd | 2.1.9 |
| Process-One | Ejabberd | 2.1.10 |
| Process-One | Ejabberd | 2.1.11 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-6169?
The TLS driver in ejabberd before 2.1.12 supports (1) SSLv2 and (2) weak SSL ciphers, which makes it easier for remote attackers to obtain sensitive information via a brute-force attack.
How severe is CVE-2013-6169?
Severity scoring for CVE-2013-6169 is pending analysis. The EPSS model estimates a 1.59% probability of exploitation in the next 30 days.
How do I fix CVE-2013-6169?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
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 2013
- CVE-2013-6162Cross-site scripting (XSS) vulnerability in Code-Crafters Ab…
- CVE-2013-6163Multiple cross-site scripting (XSS) vulnerabilities in Proje…
- CVE-2013-6164SQL injection vulnerability in view/objectDetail.php in Proj…
- CVE-2013-6166Google Chrome before 29 sends HTTP Cookie headers without fi…
- CVE-2013-6167Mozilla Firefox through 27 sends HTTP Cookie headers without…
- CVE-2013-6168Cross-site scripting (XSS) vulnerability in Zikula Applicati…
- CVE-2013-6170Juniper Junos 10.0 before 10.0S28, 10.4 before 10.4R7, 11.1 …
- CVE-2013-6171checkpassword-reply in Dovecot before 2.2.7 performs setuid …
- CVE-2013-6172steps/utils/save_pref.inc in Roundcube webmail before 0.8.7 …
- CVE-2013-6173Multiple cross-site request forgery (CSRF) vulnerabilities i…
- CVE-2013-6174Multiple open redirect vulnerabilities in xAdmin in EMC Docu…
- CVE-2013-6175Multiple cross-site scripting (XSS) vulnerabilities in EMC D…
Are you affected by CVE-2013-6169?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
