CVE-2020-28429
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. O3 Security confirms whether CVE-2020-28429 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Command Injection in geojson2kml
Real-World Exposure
geojson2kmlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
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 |
Research 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2020-28429 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2020-28429. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2020-28429 in your dependencies?
O3 detects CVE-2020-28429 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.