# CVE-2020-28443: Command Injection

> Attackers can execute arbitrary commands via the sonar-wrapper npm library, potentially compromising the host system.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wr4v-3f2h-6hhh

## What is CVE-2020-28443?

CVE-2020-28443 is a critical command injection vulnerability in sonar-wrapper, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects all versions of package sonar-wrapper. The injection point is located in lib/sonarRunner.js.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2020-28443?

2 open source packages ship an affected version, including sonar-wrapper. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sonar-wrapper` | npm | All versions to 0.1.3 | None |
| `sonar-wrapper` | npm | All versions to 0.1.3 | None |

Products: Sonar-Wrapper Project Sonar-Wrapper.

## How do I fix CVE-2020-28443?

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

## Is CVE-2020-28443 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-28443 and fix it if it is affected.

What it is: CVE-2020-28443 is a critical command injection vulnerability in sonar-wrapper, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-28443 in the wild and no public exploit code.

Affected packages and fixed versions:
- sonar-wrapper (npm): affected all versions up to 0.1.3; no fix listed
- sonar-wrapper (npm): affected all versions up to 0.1.3; no fix listed

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

## Sources

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

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