CVE-2014-8760 json
ejabberd before 2.1.13 does not enforce the starttls_required setting when compression is used, which causes clients to establish connectio…
published 2014-10-25 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-8591
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
ejabberd before 2.1.13 does not enforce the starttls_required setting when compression is used, which causes clients to establish connections without encryption.
Patch / fix
- ejabberd Debian 14, Debian 13, Debian 12 14.07-3
debian advisories DEBIAN-CVE-2014-8760
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-2014-8760 updated cvss 5.8
ejabberd: clients can unexpectedly connect without encryption
-
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.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
github.com
/processone/ejabberd/commit/7bdc1151b
patch
-
mandriva.com
/security/advisories?name=MDVSA-2014:207
vendor-advisory, patch
-
mandriva.com
/security/advisories?name=MDVSA-2015:175
vendor-advisory
-
advisories.mageia.org
/MGASA-2014-0417.html
vendor-advisory
-
seclists.org
/oss-sec/2014/q4/312
mailing-list
-
mail.jabber.org
/pipermail/operators/2014-October/002438.html
mailing-list
- bugzilla.redhat.com /show_bug.cgi?id=1153839
-
securityfocus.com
/bid/70415
vdb-entry
Sources
- CVE List CVE-2014-8760
- NVD CVE-2014-8760
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.