Little CMS Color Engine vulnerabilitiesRanked by how likely they are to be used.

Product23 versions
The short answer

Little CMS Color Engine is made by Littlecms. We track 7 published vulnerabilities in it, across 23 versions. None of them is on the list of flaws known to be exploited today. If you run Little CMS Color Engine, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Little CMS Color Engine vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Little CMS Color Engine's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Little CMS Color Engine flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 6.2%

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

    CVSS9.8Published7 May 2016
  2. 4.0%

    Multiple stack-based buffer overflows in LittleCMS (aka lcms or liblcms) 1.19 and earlier allow remote attackers to cause a denial of service (crash) via a crafted (1) ICC color profile to the icctrans utility or (2)...

    CVSS4.3Published28 Sep 2013
  3. 2.8%

    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)...

    CVSS5.0Published21 Jan 2014
  4. 2.8%

    Buffer overflow in the ReadEmbeddedTextTag function in src/cmsio1.c in Little cms color engine (aka lcms) before 1.16 allows attackers to have an unknown impact via vectors related to a length parameter inconsistency...

    CVSS10.0Published3 Dec 2008
  5. 2.8%

    The Type_MLU_Read function in cmstypes.c in Little CMS (aka lcms2) allows remote attackers to obtain sensitive information or cause a denial of service via an image with a crafted ICC profile, which triggers an...

    CVSS7.1Published3 Feb 2017
  6. 2.2%

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

    CVSS10.0Published3 Dec 2008
  7. 1.7%

    Little CMS (aka Little Color Management System) 2.9 has an integer overflow in the AllocateDataSet function in cmscgats.c, leading to a heap-based buffer overflow in the SetData function via a crafted file in the...

    CVSS5.5Published4 Sep 2018
Precursor Intelligence

Running Little CMS Color Engine? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 7 published vulnerabilities listed under the name Little CMS Color Engine, across 23 versions.

None of Little CMS Color Engine's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Little CMS Color Engine. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.