CVE-2020-28436 — google-cloudstorage-comma…
CRITICALCVE-2020-28436 is a critical-severity (CVSS 9.8) CWE-77 vulnerability in google-cloudstorage-commands. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
google-cloudstorage-commands Command Injection vulnerability
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
google-cloudstorage-commandsnpmDescription
A command injection vulnerability affects all versions of the deprecated package google-cloudstorage-commands.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | google-cloudstorage-commands | all versions | No fix |
Affected Products
google-cloudstorage-commandsgoogle-cloudstorage-commands_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 google-cloudstorage-commands, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of google-cloudstorage-commands for CVE-2020-28436. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
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.
Frequently Asked Questions
Is CVE-2020-28436 in your dependencies?
Find it across npm, including transitive dependencies.