# CVE-2020-28490: Command Injection


- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Feb 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6qpr-9mc5-7gch, SNYK-JS-ASYNCGIT-1064877

## What is CVE-2020-28490?

CVE-2020-28490 is a critical vulnerability in async-git, published on 18 Feb 2021. 

### Official description

The package async-git before 1.13.2 are vulnerable to Command Injection via shell meta-characters (back-ticks). For example: git.reset('atouch HACKEDb')

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `async-git` | npm | All versions | 1.13.2 |
| `async-git` | npm | All versions | 1.13.2 |

Products: Async-Git Project Async-Git.

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

Upgrade async-git to 1.13.2 or later.

## Is CVE-2020-28490 being exploited?

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

## Other vulnerabilities in async-git

- [CVE-2021-3190](https://insights.sbomify.com/CVE-2021-3190/): OS Command Injection in async-git (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28490 is a critical vulnerability in async-git, published on 18 Feb 2021. 
Exploitation: There is no known exploitation of CVE-2020-28490 in the wild and no public exploit code.

Affected packages and fixed versions:
- async-git (npm): affected all versions; fixed in 1.13.2
- async-git (npm): affected all versions; fixed in 1.13.2

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

## Sources

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

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