dbcve.org
Little Cms Color EngineApplication · Littlecms

CVE-2013-7455

CRITICAL · 9.8 CVSS v3.0 Published 2016-05-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Double free vulnerability in the DefaultICCintents function in cmscnvrt.c in liblcms2 in Little CMS 2.x before 2.6 allows remote attackers to execute arbitrary code via a malformed ICC profile that triggers an error in the default intent handler.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Little Cms Color EngineApplication
Affected:= 2.0= 2.1= 2.2= 2.3= 2.4= 2.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Recommended fix High confidence

Little CMS 2.6 or later (e.g., 2.6, 2.7, 2.8, latest stable release)

  1. 1. Identify all applications and libraries that link to liblcms2 in your environment
  2. 2. Locate the installed Little CMS library version (check /usr/lib/liblcms2* or similar paths, or use 'dpkg -l' on Debian/Ubuntu, 'rpm -qa' on RHEL/CentOS)
  3. 3. Obtain the fixed Little CMS version 2.6 or later from the official repository: https://github.com/mm2/Little-CMS/releases
  4. 4. Download the source code or pre-built packages for version 2.6 or newer
  5. 5. Rebuild or reinstall the library using the fixed version (e.g., './configure && make && make install' from source, or install via package manager once updated packages are available)
  6. 6. Rebuild any applications that statically link against liblcms2 to ensure they use the fixed library
  7. 7. Verify the fix by checking that the library version is 2.6 or later: 'pkg-config --modversion lcms2'
  8. 8. Test that applications using the color engine function normally with the new library
Caveat Minimal risk - this is a bugfix release addressing a security vulnerability; no API/ABI breaks are expected between 2.x versions

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $2,300. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-7455 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-7455 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data