# CVE-2007-1351: Integer overflow in n/a

> Remote authenticated users can execute arbitrary code via crafted BDF fonts due to an integer overflow in libXfont and freetype.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-1351, DSA-1454-1, GHSA-cmmx-w757-8p75, RHSA-2007:0150

## What is CVE-2007-1351?

CVE-2007-1351 is a high-severity vulnerability in Openbsd Openbsd, published on 6 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Integer overflow in the bdfReadCharacters function in bdfread.c in (1) X.Org libXfont before 20070403 and (2) freetype 2.3.2 and earlier allows remote authenticated users to execute arbitrary code via crafted BDF fonts, which result in a heap overflow.

Weakness: CWE-189

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

It affects 9 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `freetype` | Red Hat:enterprise_linux:3::as | All versions | 0:2.1.4-6.el3 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:2.1.4-6.el3 |
| `freetype-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:2.1.4-6.el3 |
| `freetype` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.1.4-6.el3 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.1.4-6.el3 |
| `freetype-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.1.4-6.el3 |
| `freetype` | Red Hat:enterprise_linux:3::es | All versions | 0:2.1.4-6.el3 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:2.1.4-6.el3 |
| `freetype-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:2.1.4-6.el3 |
| `freetype` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.1.4-6.el3 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.1.4-6.el3 |
| `freetype-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.1.4-6.el3 |
| `freetype` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.9-5.el4 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.9-5.el4 |
| `freetype-demos` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.9-5.el4 |
| `freetype-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.9-5.el4 |
| `freetype-utils` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.9-5.el4 |
| `freetype` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.9-5.el4 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.9-5.el4 |
| `freetype-demos` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.9-5.el4 |
| `freetype-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.9-5.el4 |
| `freetype-utils` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.9-5.el4 |
| `freetype` | Red Hat:enterprise_linux:4::es | All versions | 0:2.1.9-5.el4 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.1.9-5.el4 |
| `freetype-demos` | Red Hat:enterprise_linux:4::es | All versions | 0:2.1.9-5.el4 |
| `freetype-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.1.9-5.el4 |
| `freetype-utils` | Red Hat:enterprise_linux:4::es | All versions | 0:2.1.9-5.el4 |
| `freetype` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.1.9-5.el4 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.1.9-5.el4 |
| `freetype-demos` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.1.9-5.el4 |
| `freetype-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.1.9-5.el4 |
| `freetype-utils` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.1.9-5.el4 |
| `freetype` | Red Hat:enterprise_linux:5::client | All versions | 0:2.2.1-17.el5 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.2.1-17.el5 |
| `freetype-demos` | Red Hat:enterprise_linux:5::client | All versions | 0:2.2.1-17.el5 |
| `freetype-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.2.1-17.el5 |
| `freetype` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.2.1-17.el5 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.2.1-17.el5 |
| `freetype-demos` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.2.1-17.el5 |
| `freetype-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.2.1-17.el5 |

Products: Mandrakesoft Mandrake Multi Network Firewall, Openbsd Openbsd, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Linux Advanced Workstation, Rpath Rpath Linux, Ubuntu Ubuntu Linux, X.org Libxfont, Xfree86 Project X11r6.

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

Upgrade to a fixed version.

## Is CVE-2007-1351 being exploited?

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

## Other vulnerabilities in Openbsd Openbsd

- [CVE-2007-1352](https://insights.sbomify.com/CVE-2007-1352/): Integer overflow in n/a (low 3.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1351 is a high-severity vulnerability in Openbsd Openbsd, published on 6 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-1351 in the wild and no public exploit code.

Affected product: Openbsd Openbsd. 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-1351/ (Markdown: https://insights.sbomify.com/CVE-2007-1351/index.md)
```

## Sources

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

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