CVE-2022-2583 is a low-severity (CVSS 3.7) CWE-362 vulnerability in github.com/ntbosscher/gobase. A fix is available for github.com/ntbosscher/gobase — see the affected versions and patch details below.
Race condition in github.com/ntbosscher/gobase
Exploitation Status
No confirmed exploitation observed yet
- 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-2022-2583.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-2583 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/ntbosscher/gobaseReal-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
Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-h2x7-2ff6-v32p. This link is maintained to preserve external references.
Original Description
A race condition can cause incorrect HTTP request routing.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/ntbosscher/gobase | all versions | 0.7.2go get github.com/ntbosscher/gobase@v0.7.2 |
Affected Products
gobasegobase_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ntbosscher/gobase, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/ntbosscher/gobase to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2583 is resolved across your whole dependency graph.
Workarounds
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.
Frequently Asked Questions
Is CVE-2022-2583 in your dependencies?
Find it across Go, including transitive dependencies.