CVE-2022-2584 is a high-severity (CVSS 7.5) Buffer Overflow vulnerability in github.com/ipld/go-codec-dagpb. A fix is available for github.com/ipld/go-codec-dagpb — see the affected versions and patch details below.
Panic when decoding invalid blocks in github.com/ipld/go-codec-dagpb
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-2584.
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/ipld/go-codec-dagpbReal-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-g3vv-g2j5-45f2. This link is maintained to preserve external references.
Original Description
go-codec-dagpb is an implementation of the DAG-PB spec for Go. The dag-pb codec can panic when decoding invalid blocks. This issue has been patched in version 1.3.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/ipld/go-codec-dagpb | all versions | 1.3.1go get github.com/ipld/go-codec-dagpb@v1.3.1 |
Affected Products
go-codec-dagpbprotocolDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ipld/go-codec-dagpb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/ipld/go-codec-dagpb to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2584 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Frequently Asked Questions
Is CVE-2022-2584 in your dependencies?
Find it across Go, including transitive dependencies.