# CVE-2013-7455: Use after free in n/a

> Remote attackers can execute arbitrary code via a malformed ICC profile due to a double free vulnerability in the Little CMS library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-7455, GHSA-wv94-377g-rv89, UBUNTU-CVE-2013-7455, USN-2961-1

## What is CVE-2013-7455?

CVE-2013-7455 is a critical use after free vulnerability in n/a, published on 7 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2013-7455?

It affects 1 product.


Products: Littlecms Little Cms Color Engine.

## How do I fix CVE-2013-7455?

Upgrade to a fixed version.

## Is CVE-2013-7455 being exploited?

There is no known exploitation of CVE-2013-7455 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-4160](https://insights.sbomify.com/CVE-2013-4160/): Null dereference in n/a (medium 5.0)
- [CVE-2013-4276](https://insights.sbomify.com/CVE-2013-4276/): Memory corruption in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7455 and fix it if it is affected.

What it is: CVE-2013-7455 is a critical use after free vulnerability in n/a, published on 7 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-7455 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-7455/ (Markdown: https://insights.sbomify.com/CVE-2013-7455/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-7455
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-7455
- OSV: https://osv.dev/vulnerability/CVE-2013-7455

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-7455/
Summaries are generated and may contain mistakes; the official description above is the record.