CVE-2013-4160 json
Little CMS (lcms2) before 2.5, as used in OpenJDK 7 and possibly other products, allows remote attackers to cause a denial of service (NULL…
published 2014-01-21 12 y ago modified 2026-06-16 4 mo ago also EUVD-2013-4085
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Little CMS (lcms2) before 2.5, as used in OpenJDK 7 and possibly other products, allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via vectors related to (1) cmsStageAllocLabV2ToV4curves, (2) cmsPipelineDup, (3) cmsAllocProfileSequenceDescription, (4) CurvesAlloc, and (5) cmsnamed.
Patch / fix
- lcms2 Debian 14, Debian 13, Debian 12 2.2+git20110628-2.3
debian advisories DEBIAN-CVE-2013-4160
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-2013-4160 updated cvss 4.6
CMS: multiple potential flaws
-
Red Hat Enterprise Linux 7 lcms2, lcms2-utilsnot 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
2.81% chance of exploitation in the next 30 days, higher than 86% 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 |
References
- github.com /mm2/Little-CMS/commit/91c2db7f2559be504211b283bc3a2c631d6f06d9
-
ubuntu.com
/usn/USN-1911-1
vendor-advisory
-
openwall.com
/lists/oss-security/2013/07/18/7
mailing-list
-
mail.openjdk.java.net
/pipermail/distro-pkg-dev/2013-July/023895.html
mailing-list
- bugzilla.novell.com /show_bug.cgi?id=826097#c9
-
openwall.com
/lists/oss-security/2013/07/22/1
mailing-list
Sources
- CVE List CVE-2013-4160
- NVD CVE-2013-4160
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.