# CVE-2022-25514: Memory corruption in n/a

> A heap-buffer-overflow in stb_truetype.h allows attackers to cause denial of service or execute arbitrary code via malicious TrueType fonts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2022
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-5hw4-hqhq-pf4g

## What is CVE-2022-25514?

CVE-2022-25514 is a high-severity memory corruption vulnerability in n/a, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

stb_truetype.h v1.26 was discovered to contain a heap-buffer-overflow via the function ttUSHORT() at stb_truetype.h. NOTE: Third party has disputed stating that the source code has also a disclaimer that it should only be used with trusted input.

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

## Which versions are affected by CVE-2022-25514?

It affects 1 product.


Products: Nothings Stb Truetype.h.

## How do I fix CVE-2022-25514?

No fix has been published for CVE-2022-25514 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-25514 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25514 exists.

## Other vulnerabilities in n/a

- [CVE-2020-6617](https://insights.sbomify.com/CVE-2020-6617/): Denial of service in n/a (high 8.8)
- [CVE-2020-6618](https://insights.sbomify.com/CVE-2020-6618/): Memory corruption in n/a (high 8.8)
- [CVE-2020-6619](https://insights.sbomify.com/CVE-2020-6619/): Denial of service in n/a (high 8.8)
- [CVE-2020-6620](https://insights.sbomify.com/CVE-2020-6620/): Memory corruption in n/a (high 8.8)
- [CVE-2020-6621](https://insights.sbomify.com/CVE-2020-6621/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25514 and fix it if it is affected.

What it is: CVE-2022-25514 is a high-severity memory corruption vulnerability in n/a, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25514 exists.

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-2022-25514/ (Markdown: https://insights.sbomify.com/CVE-2022-25514/index.md)
```

## Sources

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

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