Skip to content
Fencer Vulns
critical 10.0

CVE-2008-5317 json

Integer signedness error in the cmsAllocGamma function in src/cmsgamma.c in Little cms color engine (aka lcms) before 1.17 allows attackers…

published 2008-12-03 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-5294

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

Integer signedness error in the cmsAllocGamma function in src/cmsgamma.c in Little cms color engine (aka lcms) before 1.17 allows attackers to have an unknown impact via a file containing a certain "number of entries" value, which is interpreted improperly, leading to an allocation of insufficient memory.

Patch / fix

  • lcms RHEL 5 1.15-1.2.2.el5_2.2
  • python-lcms RHEL 5 1.15-1.2.2.el5_2.2

red hat advisories RHSA-2009:0011

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-2008-5317 updated

lcms: unsigned -> signed integer cast issue in cmsAllocGamma

  • Red Hat Enterprise Linux (v. 5 server) lcms 1.15-1.2.2.el5_2.2, python-lcms 1.15-1.2.2.el5_2.2 Red Hat Enterprise Linux Desktop (v. 5 client) lcms 1.15-1.2.2.el5_2.2, python-lcms 1.15-1.2.2.el5_2.2 Red Hat Enterprise Linux Desktop Workstation (v. 5 client) lcms 1.15-1.2.2.el5_2.2, python-lcms 1.15-1.2.2.el5_2.2
    fixed: vendor fix RHSA-2009:0011

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.16% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness

References

Sources

Fencer Vulns 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.