CVE-2020-36569 is a critical-severity (CVSS 9.1) Improper Authentication vulnerability in github.com/nanobox-io/golang-nanoauth. A fix is available for github.com/nanobox-io/golang-nanoauth — see the affected versions and patch details below.
golang-nanoauth authentication bypass vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2020-36569.
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
github.com/nanobox-io/golang-nanoauthReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Authentication is globally bypassed in github.com/nanobox-io/golang-nanoauth between v0.0.0-20160722212129-ac0cc4484ad4 and v0.0.0-20200131131040-063a3fb69896 if ListenAndServe is called with an empty token.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/nanobox-io/golang-nanoauth | ≥ 0.0.0-20160722212129-ac0cc4484ad4&&< 0.0.0-20200131131040-063a3fb69896 | 0.0.0-20200131131040-063a3fb69896go get github.com/nanobox-io/golang-nanoauth@v0.0.0-20200131131040-063a3fb69896 |
Affected Products
golang-nanoauthdigitaloceanDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/nanobox-io/golang-nanoauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/nanobox-io/golang-nanoauth to 0.0.0-20200131131040-063a3fb69896 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-36569 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2020-36569 in your dependencies?
Find it across Go, including transitive dependencies.