# CVE-2022-28391: Command injection in n/a

> Remote attackers can execute arbitrary code or alter terminal colors via crafted DNS PTR records when BusyBox netstat is used.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Apr 2022
- **Updated:** 9 Jun 2025
- **Also known as:** ALPINE-CVE-2022-28391, AZL-41790, AZL-9311, CLSA-2022-1650376937, CLSA-2022-1650377094, CLSA-2022-1650377131, CLSA-2023-1688070489, GHSA-h8c3-8522-vxc6, MGASA-2022-0135, OESA-2022-1624

## What is CVE-2022-28391?

CVE-2022-28391 is a high-severity command injection vulnerability in n/a, published on 3 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

BusyBox through 1.35.0 allows remote attackers to execute arbitrary code if netstat is used to print a DNS PTR record's value to a VT compatible terminal. Alternatively, the attacker could choose to change the terminal's colors.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

It affects 1 product.


Products: Busybox Busybox.

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

Apply the vendor's patch.

## Is CVE-2022-28391 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-48174](https://insights.sbomify.com/CVE-2022-48174/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-42377](https://insights.sbomify.com/CVE-2021-42377/): Memory corruption in busybox (critical 9.8)
- [CVE-2016-2148](https://insights.sbomify.com/CVE-2016-2148/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-16544](https://insights.sbomify.com/CVE-2017-16544/): Code injection in n/a (high 8.8)
- [CVE-2018-1000517](https://insights.sbomify.com/CVE-2018-1000517/): Memory corruption in n/a (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28391 is a high-severity command injection vulnerability in n/a, published on 3 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-28391 in the wild and no public exploit code.

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

## Sources

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

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