# CVE-2020-28429: Command Injection

> Attackers can execute arbitrary commands via the geojson2kml npm library due to improper input handling in index.js.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w83x-fp72-p9qc

## What is CVE-2020-28429?

CVE-2020-28429 is a high-severity command injection vulnerability in geojson2kml, published on 23 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of package geojson2kml are vulnerable to Command Injection via the index.js file. PoC: var a =require("geojson2kml"); a("./","& touch JHU",function(){})

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `geojson2kml` | npm | All versions to 0.1.1 | None |
| `geojson2kml` | npm | All versions to 0.1.1 | None |

Products: Geojson2kml Project Geojson2kml.

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

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

## Is CVE-2020-28429 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-28429 exists.

Public exploit code:

- geojson2kml - Command Injection (nuclei): http/cves/2020/CVE-2020-28429.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28429 is a high-severity command injection vulnerability in geojson2kml, published on 23 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-28429 exists.

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

## Sources

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

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