# CVE-2008-5316: Memory corruption in n/a

> A buffer overflow in Little CMS allows attackers to execute arbitrary code or cause denial of service via a crafted input file.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hwr4-gr5c-2vfm

## What is CVE-2008-5316?

CVE-2008-5316 is a critical memory corruption vulnerability in n/a, published on 3 Dec 2008. 

### Official description

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 involving the contents of "the input file," a different vulnerability than CVE-2007-2741.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-5316?

It affects 2 products.


Products: Littlecms Lcms, Littlecms Little Cms Color Engine.

## How do I fix CVE-2008-5316?

Upgrade to a fixed version.

## Is CVE-2008-5316 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5317](https://insights.sbomify.com/CVE-2008-5317/): Integer overflow in n/a (critical 10.0)
- [CVE-2007-2741](https://insights.sbomify.com/CVE-2007-2741/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-0793](https://insights.sbomify.com/CVE-2009-0793/): Null dereference in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5316 and fix it if it is affected.

What it is: CVE-2008-5316 is a critical memory corruption vulnerability in n/a, published on 3 Dec 2008. 
Exploitation: There is no known exploitation of CVE-2008-5316 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-2008-5316/ (Markdown: https://insights.sbomify.com/CVE-2008-5316/index.md)
```

## Sources

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

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