# CVE-2007-5199: Memory corruption in n/a

> A single byte overflow in X.Org libXfont allows remote attackers to potentially execute arbitrary code.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 18 Aug 2017
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5199, GHSA-c8m3-98wf-r685

## What is CVE-2007-5199?

CVE-2007-5199 is a critical memory corruption vulnerability in n/a, published on 18 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A single byte overflow in catalogue.c in X.Org libXfont 1.3.1 allows remote attackers to have unspecified impact.

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

## Which versions are affected by CVE-2007-5199?

It affects 1 product.


Products: X Libxfont.

## How do I fix CVE-2007-5199?

Upgrade to a fixed version.

## Is CVE-2007-5199 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6462](https://insights.sbomify.com/CVE-2013-6462/): Memory corruption in n/a (critical 9.3)
- [CVE-2026-56001](https://insights.sbomify.com/CVE-2026-56001/): libXfont2 BitmapScaleBitmaps Integer Overflow Heap Buffer Overflow (high 8.5)
- [CVE-2026-56002](https://insights.sbomify.com/CVE-2026-56002/): libXfont2 PCF Font Parsing Heap Buffer Overflow (high 8.5)
- [CVE-2026-56003](https://insights.sbomify.com/CVE-2026-56003/): libXfont2 computeProps Property Buffer Heap Buffer Overflow (high 8.5)
- [CVE-2015-1802](https://insights.sbomify.com/CVE-2015-1802/): Memory corruption in n/a (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5199 and fix it if it is affected.

What it is: CVE-2007-5199 is a critical memory corruption vulnerability in n/a, published on 18 Aug 2017. 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-2007-5199 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-2007-5199/ (Markdown: https://insights.sbomify.com/CVE-2007-5199/index.md)
```

## Sources

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

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