CVE-2024-28180

Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification)

An attacker could send a JWE containing compressed data that used large amounts of memory and CPU when decompressed by Decrypt or DecryptMulti. Those functions now return an error if the decompressed data would exceed 250kB or 10x the compressed size (whichever is larger). Thanks to Enze Wang@Alioth and Jianjun Chen@Zhongguancun Lab (@zer0yu and @chenjj) for reporting.

CVE-2024-28180 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low 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 (4.0.1, 3.0.3, 2.6.3); upgrading removes the vulnerable code path.

Kodem intelligence

The problem is fixed in the following packages and versions:

• github.com/go-jose/go-jose/v4 version 4.0.1
• github.com/go-jose/go-jose/v3 version 3.0.3
• gopkg.in/go-jose/go-jose.v2 version 2.6.3

The problem will not be fixed in the following package because the package is archived:

• gopkg.in/square/go-jose.v2

1. What is CVE-2024-28180? CVE-2024-28180 is a medium-severity security vulnerability in github.com/go-jose/go-jose/v4 (go), affecting versions < 4.0.1. It is fixed in 4.0.1, 3.0.3, 2.6.3.
2. How severe is CVE-2024-28180? CVE-2024-28180 has a CVSS score of 4.3 (Medium). 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.
3. Which packages are affected by CVE-2024-28180?
   • github.com/go-jose/go-jose/v4 (go) (versions < 4.0.1)
   • github.com/go-jose/go-jose/v3 (go) (versions < 3.0.3)
   • gopkg.in/go-jose/go-jose.v2 (go) (versions < 2.6.3)
   • gopkg.in/square/go-jose.v2 (go) (versions <= 2.6.0)
4. Is there a fix for CVE-2024-28180? Yes. CVE-2024-28180 is fixed in 4.0.1, 3.0.3, 2.6.3. Upgrade to this version or later.
5. Is CVE-2024-28180 exploitable, and should I be worried? Whether CVE-2024-28180 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
6. What actually determines whether CVE-2024-28180 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.
7. How do I fix CVE-2024-28180?
   • Upgrade github.com/go-jose/go-jose/v4 to 4.0.1 or later
   • Upgrade github.com/go-jose/go-jose/v3 to 3.0.3 or later
   • Upgrade gopkg.in/go-jose/go-jose.v2 to 2.6.3 or later