# CVE-2020-36379: Vulnerability in remove function leads to arbitrary code execution via filePath parameters

> Attackers can execute arbitrary code via the filePath parameter in the remove function of the aaptjs Node.js library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9cq3-fj2h-ggj5

## What is CVE-2020-36379?

CVE-2020-36379 is a critical command injection vulnerability in n/a, published on 31 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the remove function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.

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

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

2 open source packages ship an affected version, including aaptjs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aaptjs` | npm | All versions to 1.3.1 | None |
| `aaptjs` | npm | All versions to 1.3.1 | None |

Products: Aaptjs Project Aaptjs.

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

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

## Is CVE-2020-36379 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-26707](https://insights.sbomify.com/CVE-2020-26707/): Command injection in n/a (critical 9.8)
- [CVE-2020-36376](https://insights.sbomify.com/CVE-2020-36376/): Vulnerability in list function leads to arbitrary code execution via filePath parameters (critical 9.8)
- [CVE-2020-36377](https://insights.sbomify.com/CVE-2020-36377/): Vulnerability in dump function leads to arbitrary code execution via filePath parameters (critical 9.8)
- [CVE-2020-36378](https://insights.sbomify.com/CVE-2020-36378/): Vulnerability in packageCmd function leads to arbitrary code execution via filePath parameters (critical 9.8)
- [CVE-2020-36380](https://insights.sbomify.com/CVE-2020-36380/): Vulnerability in crunch function leads to arbitrary code execution via filePath parameters (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36379 is a critical command injection vulnerability in n/a, published on 31 Oct 2021. 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-36379 in the wild and no public exploit code.

Affected packages and fixed versions:
- aaptjs (npm): affected all versions up to 1.3.1; no fix listed
- aaptjs (npm): affected all versions up to 1.3.1; 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-36379/ (Markdown: https://insights.sbomify.com/CVE-2020-36379/index.md)
```

## Sources

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

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