What is CVE-2022-2584?

CVE-2022-2584 is a high-severity security vulnerability in github.com/ipld/go-codec-dagpb (go), affecting versions < 1.3.1. It is fixed in 1.3.1.

How severe is CVE-2022-2584?

CVE-2022-2584 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/ipld/go-codec-dagpb are affected by CVE-2022-2584?

github.com/ipld/go-codec-dagpb (go) versions < 1.3.1 is affected.

Is there a fix for CVE-2022-2584?

Yes. CVE-2022-2584 is fixed in 1.3.1. Upgrade to this version or later.

Is CVE-2022-2584 exploitable, and should I be worried?

Whether CVE-2022-2584 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-2584 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-2584?

Upgrade github.com/ipld/go-codec-dagpb to 1.3.1 or later.

CVE-2022-2584 in github.com/ipld/go-codec-dagpb

Q: How severe is CVE-2022-2584?

CVE-2022-2584 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/ipld/go-codec-dagpb are affected by CVE-2022-2584?

github.com/ipld/go-codec-dagpb (go) versions < 1.3.1 is affected.

Q: Is there a fix for CVE-2022-2584?

Yes. CVE-2022-2584 is fixed in 1.3.1. Upgrade to this version or later.

Q: Is CVE-2022-2584 exploitable, and should I be worried?

Whether CVE-2022-2584 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-2584 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-2584?

Upgrade github.com/ipld/go-codec-dagpb to 1.3.1 or later.

Summary

ipld/go-codec-dagpb panics when processing certain blocks

Impact

Decoding certain blocks using the go-ipld-prime version of the dag-pb codec (go-codec-dagpb) can cause a panic. The panic comes from an assumption that the reported link length is accurate, but if the block ends before that reported length then it’s a buffer overread.

CVE-2022-2584 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.3.1); upgrading removes the vulnerable code path.

Affected versions

github.com/ipld/go-codec-dagpb (< 1.3.1)

Security releases

github.com/ipld/go-codec-dagpb → 1.3.1 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The issue is fixed in v1.3.1 and above.

Consumers can discover the versions of go-codec-dagpb in a module's dependency graph using the following command in the module root:

go mod graph | grep go-codec-dagpb

Workarounds

You can work around this issue without upgrading by recovering panics higher in the call stack of the goroutine that calls the defective code.

For more information

If you have any questions or comments about this advisory:

Ask in IPFS Discord #ipld-chatter
Open an issue in go-codec-dagpb

Frequently Asked Questions

What is CVE-2022-2584? CVE-2022-2584 is a high-severity security vulnerability in github.com/ipld/go-codec-dagpb (go), affecting versions < 1.3.1. It is fixed in 1.3.1.
How severe is CVE-2022-2584? CVE-2022-2584 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/ipld/go-codec-dagpb are affected by CVE-2022-2584? github.com/ipld/go-codec-dagpb (go) versions < 1.3.1 is affected.
Is there a fix for CVE-2022-2584? Yes. CVE-2022-2584 is fixed in 1.3.1. Upgrade to this version or later.
Is CVE-2022-2584 exploitable, and should I be worried? Whether CVE-2022-2584 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-2584 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-2584? Upgrade github.com/ipld/go-codec-dagpb to 1.3.1 or later.