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

> Attackers can trigger a buffer overflow in xterm via crafted text when Sixel support is enabled, potentially leading to code execution or crashes.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** 31 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** ALSA-2025:14075, AZL-8456, DEBIAN-CVE-2022-24130, DLA-2913-1, GHSA-5v7p-cf4c-24jq, MGASA-2022-0051, OESA-2022-1563, OESA-2022-2072, RHSA-2025:14075, RLSA-2025:14075, SUSE-SU-2022:3952-1, SUSE-SU-2022:3953-1, UBUNTU-CVE-2022-24130, openSUSE-SU-2024:12733-1

## What is CVE-2022-24130?

CVE-2022-24130 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 31 Jan 2022. 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

xterm through Patch 370, when Sixel support is enabled, allows attackers to trigger a buffer overflow in set_sixel in graphics_sixel.c via crafted text.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xterm` | AlmaLinux:9 | All versions | 366-12.el9_6 |
| `xterm-resize` | AlmaLinux:9 | All versions | 366-12.el9_6 |
| `xterm` | Red Hat:enterprise_linux:9::appstream | All versions | 0:366-12.el9_6 |
| `xterm-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:366-12.el9_6 |
| `xterm-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:366-12.el9_6 |
| `xterm-resize` | Red Hat:enterprise_linux:9::appstream | All versions | 0:366-12.el9_6 |
| `xterm-resize-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:366-12.el9_6 |
| `xterm` | Rocky Linux:9 | All versions | 0:366-12.el9_6 |
| `xterm` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 330-150200.11.6.1 |
| `xterm` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 330-150200.11.6.1 |
| `xterm` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 308-5.6.1 |
| `xterm` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 308-5.6.1 |
| `xterm` | openSUSE:Leap 15.3 | All versions | 330-150200.11.6.1 |
| `xterm` | openSUSE:Leap 15.4 | All versions | 330-150200.11.6.1 |
| `mlterm` | openSUSE:Tumbleweed | All versions | 3.9.2-3.1 |

Products: Debian Debian Linux, Fedoraproject Fedora, Invisible-Island Xterm.

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

Apply the vendor's patch.

## Is CVE-2022-24130 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24130 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 31 Jan 2022. 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-2022-24130 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-24130/ (Markdown: https://insights.sbomify.com/CVE-2022-24130/index.md)
```

## Sources

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

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