CVE-2022-27470

7.8 HIGH 1.0% exploit odds Fix listed

What it is

SDL_ttf v2.0.18 and below was discovered to contain an arbitrary memory write via the function TTF_RenderText_Solid(). This vulnerability is triggered via a crafted TTF file.

At a glance

Exploitability: Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.
Exploit odds: 1.0% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2022-05-04 03:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-17 04:37 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 1.0% in the next 30 days (EPSS).
Severity: 7.8 HIGH (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2022-05-04 03:15 UTC
Last modified: 2026-06-17 04:37 UTC
Exploit probability: 1.0% · EPSS, next 30 days
Weakness: CWE-787 · Out-of-bounds write
Record status: Modified

Affected

Libsdl Sdl Ttf ≤ 2.0.18
Fedoraproject Fedora 34
Fedoraproject Fedora 35
Fedoraproject Fedora 36

Attack profile CVSS 3.1 · 7.8

Attack vector: Local
Complexity: Low
Privileges needed: None
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-27470.md and follow it. Check whether this project is affected by CVE-2022-27470. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record