CVE-2012-3514 json
OCaml Xml-Light Library before r234 computes hash values without restricting the ability to trigger hash collisions predictably, which allo…
published 2012-08-25 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-3469
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
OCaml Xml-Light Library before r234 computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via unspecified vectors.
Patch / fix
- xml-light Debian 14, Debian 13, Debian 12 2.2-15
debian advisories DEBIAN-CVE-2012-3514
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-3514 updated cvss 5.0
ocaml-xml-light: hash table collisions CPU usage DoS
-
Red Hat Enterprise Linux 6 ocaml-xml-lightaffected: no fix planned “Will not fix”
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.50% chance of exploitation in the next 30 days, higher than 74% 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:N/I:N/A:P |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
mandriva.com
/security/advisories?name=MDVSA-2013:107
vendor-advisory
-
secunia.com
/advisories/50311
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/55114
vdb-entry
-
openwall.com
/lists/oss-security/2012/08/21/2
mailing-list
- wiki.mageia.org /en/Support/Advisories/MGASA-2012-0266
Sources
- CVE List CVE-2012-3514
- NVD CVE-2012-3514
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.