# CVE-2024-43700: Memory corruption in xfpt

> A stack-based buffer overflow in xfpt allows arbitrary code execution when a user processes a specially crafted file.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Aug 2024
- **Updated:** 30 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-43700, DLA-3977-1, GHSA-436p-pp82-ppwq, UBUNTU-CVE-2024-43700, USN-7192-1

## What is CVE-2024-43700?

CVE-2024-43700 is a high-severity memory corruption vulnerability in Philip Hazel xfpt, published on 29 Aug 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

xfpt versions prior to 1.01 fails to handle appropriately some parameters inside the input data, resulting in a stack-based buffer overflow vulnerability. When a user of the affected product is tricked to process a specially crafted file, arbitrary code may be executed on the user's environment.

Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-43700?

It affects 1 product.


Products: Philiphazel Xfpt.

## How do I fix CVE-2024-43700?

Upgrade to a fixed version.

## Is CVE-2024-43700 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-43700 and fix it if it is affected.

What it is: CVE-2024-43700 is a high-severity memory corruption vulnerability in Philip Hazel xfpt, published on 29 Aug 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-43700 in the wild and no public exploit code.

Affected product: Philip Hazel xfpt. 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-2024-43700/ (Markdown: https://insights.sbomify.com/CVE-2024-43700/index.md)
```

## Sources

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

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