# CVE-2022-4883: Command injection in libXpm

> Attackers can execute arbitrary code by manipulating the PATH environment variable when libXpm processes compressed image files.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 7 Feb 2023
- **Updated:** 20 Mar 2025
- **Also known as:** ALPINE-CVE-2022-4883, AZL-13248, DEBIAN-CVE-2022-4883, GHSA-75px-q76w-83rc, JLSEC-2026-285, RHSA-2023:0377, UBUNTU-CVE-2022-4883

## What is CVE-2022-4883?

CVE-2022-4883 is a high-severity command injection vulnerability in libXpm, published on 7 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in libXpm. When processing files with .Z or .gz extensions, the library calls external programs to compress and uncompress files, relying on the PATH environment variable to find these programs, which could allow a malicious user to execute other programs by manipulating the PATH environment variable.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libXpm` | Red Hat:enterprise_linux:7::client | All versions | 0:3.5.12-2.el7_9 |
| `libXpm-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:3.5.12-2.el7_9 |
| `libXpm-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:3.5.12-2.el7_9 |
| `libXpm-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.5.12-2.el7_9 |
| `libXpm-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.5.12-2.el7_9 |
| `libXpm` | Red Hat:enterprise_linux:7::server | All versions | 0:3.5.12-2.el7_9 |
| `libXpm-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:3.5.12-2.el7_9 |
| `libXpm-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:3.5.12-2.el7_9 |
| `libXpm` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.5.12-2.el7_9 |
| `libXpm-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.5.12-2.el7_9 |
| `libXpm-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.5.12-2.el7_9 |

Products: X.org Libxpm.

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

Apply the vendor's patch.

## Is CVE-2022-4883 being exploited?

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

## Other vulnerabilities in libXpm

- [CVE-2016-10164](https://insights.sbomify.com/CVE-2016-10164/): Integer overflow in n/a (critical 9.8)
- [CVE-2022-46285](https://insights.sbomify.com/CVE-2022-46285/): Denial of service in libXpm (high 7.5)
- [CVE-2022-44617](https://insights.sbomify.com/CVE-2022-44617/): Denial of service in libXpm (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4883 is a high-severity command injection vulnerability in libXpm, published on 7 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4883 in the wild and no public exploit code.

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

## Sources

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

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