CVE-2020-28429 — geojson2kml
CRITICALCVE-2020-28429 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in geojson2kml. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.
Command Injection in geojson2kml
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-28429 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
geojson2kmlnpmDescription
All versions up to and including version 0.1.1 of package geojson2kml are vulnerable to Command Injection via the index.js file.
PoC:
var a =require("geojson2kml");
a("./","& touch JHU",function(){})
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | geojson2kml | all versions | No fix |
Affected Products
geojson2kmlgeojson2kml_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for geojson2kml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of geojson2kml has shipped for CVE-2020-28429 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
How to detect CVE-2020-28429
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2020-28429 -u https://target- Template
- geojson2kml - Command Injection
- Severity
- critical
- Impact
- Successful exploitation of this vulnerability could result in unauthorized access, remote code execution, privilege escalation
- Remediation
- Do not use geojson2kml. There is no fixed version for geojson2kml.
Template by ProjectDiscovery nuclei-templates (eeche, chae1xx1os, persona-twotwo), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2020-28429 in your dependencies?
Find it across npm, including transitive dependencies.