CVE-2013-6169: The TLS driver in ejabberd before 2.1.12 supports (1) SSLv2 and (2) weak SSL ciphers, which makes it easier fo

Q: How do I fix CVE-2013-6169?

ejabberd: upgrade to newer than 2.1.12. Exact commands for each OS are on this page.

Q: Is CVE-2013-6169 being exploited?

CVE-2013-6169 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2013-6169 affect?

CVE-2013-6169 affects ejabberd. Severity is medium (CVSS 4.3). 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.

Q: How urgent is CVE-2013-6169?

Priority 34/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2013-6169 is a medium-severity flaw (CVSS 4.3) affecting ejabberd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Weakness	CWE-310
Published	2013-10-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: process-one

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2013-10-17 23:55 UTCPublished CVE record published
2026-06-17 00:00 UTCUpdated Record last modified

process-one ejabberd UPGRADE

Affected: <= 2.1.12 · 0.9 · 0.9.1 · 0.9.8 · 1.0.0 · 1.1.0 · 1.1.1 · 1.1.1.0

Fixed in: newer than 2.1.12

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy ejabberd || rpm -q ejabberd || ejabberd --version

2. UPGRADE to newer than 2.1.12 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ejabberd

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ejabberd

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-6169?

ejabberd: upgrade to newer than 2.1.12. Exact commands for each OS are on this page.

Is CVE-2013-6169 being exploited?

CVE-2013-6169 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-6169 affect?

CVE-2013-6169 affects ejabberd. Severity is medium (CVSS 4.3). 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 urgent is CVE-2013-6169?

Priority 34/100. No elevated risk signals yet.

Related CVEs

CVE-2014-8760 MEDIUM 5.0 UPGRADE ejabberd before 2.1.13 does not enforce the starttls_required setting when compression is used, which causes c

References

← Back to latest CVEs