CVE-2024-28180: Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification)

Published Mar 7, 2024
·
Updated

Impact 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.

Patches 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

Other sources

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

Microsoft

Package jose aims to provide an implementation of the Javascript Object Signing and Encryption set of standards. 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). This vulnerability has been patched in versions 4.0.1, 3.0.3 and 2.6.3.

NVD

Affected Software

61 affected componentsFixes available
go/gopkg.in/square/go-jose.v2<=2.6.0
go/gopkg.in/go-jose/go-jose.v2<2.6.3
2.6.3
go/github.com/go-jose/go-jose/v3<3.0.3
3.0.3
go/github.com/go-jose/go-jose/v4<4.0.1
4.0.1
redhat/go-jose<4.0.1
4.0.1
redhat/go-jose<3.0.3
3.0.3
redhat/go-jose<2.6.3
2.6.3
Go-jose Project Go-jose>=2.0.0<2.6.3
Go-jose Project Go-jose>=3.0.0<3.0.3
Go-jose Project Go-jose>=4.0.0<4.0.1
Fedoraproject Fedora>=38<=40
Microsoft cbl2 telegraf 1.29.4-15
Microsoft azl3 cert-manager 1.11.2-8
Microsoft azl3 skopeo 1.14.1-1
Microsoft azl3 kubernetes 1.30.10-7
Microsoft cbl2 kube-vip-cloud-provider 0.0.2-22
Microsoft azl3 telegraf 1.29.4-1
Microsoft cbl2 kubernetes 1.28.4-17
Microsoft cbl2 cri-o 1.22.3-14
Microsoft cbl2 keda 2.4.0-29
Microsoft azl3 influxdb 2.7.5-5
Microsoft azl3 containerized-data-importer 1.57.0-14
Microsoft cbl2 telegraf 1.29.4-15
Microsoft azl3 packer 1.9.5-9
Microsoft cbl2 cert-manager 1.11.2-22
Microsoft azl3 dcos-cli 1.2.0-18
Microsoft azl3 keda 2.4.0-15
Microsoft azl3 containerd 1.7.13-8
Microsoft azl3 moby-containerd-cc 1.7.7-9
Microsoft cbl2 skopeo 1.14.2-10
Microsoft cbl2 rook 1.6.2-26
Microsoft cbl2 packer 1.9.5-12
Microsoft azl3 kubernetes 1.30.1-1
Microsoft cbl2 moby-containerd 1.6.26-11
Microsoft cbl2 moby-containerd-cc 1.7.7-11
Microsoft cbl2 dcos-cli 1.2.0-21
Microsoft cbl2 influxdb 2.6.1-22
Microsoft cbl2 containerized-data-importer 1.55.0-23
Microsoft azl3 influxdb 2.7.3-9
Microsoft azl3 containerized-data-importer 1.57.0-9
Microsoft azl3 dcos-cli 1.2.0-16
Microsoft azl3 moby-containerd-cc 1.7.7-6
Microsoft azl3 telegraf 1.31.0-1
Microsoft azl3 skopeo 1.14.4-1
Microsoft azl3 cert-manager 1.12.12-1
Microsoft azl3 packer 1.9.5-6
Microsoft cbl2 moby-containerd 1.6.26-9
Microsoft azl3 keda 2.14.0-1
Microsoft cbl2 kube-vip-cloud-provider 0.0.2-19
Microsoft cbl2 kubernetes 1.28.4-12
Microsoft cbl2 rook 1.6.2-23
Microsoft cbl2 moby-containerd-cc 1.7.7-9
Microsoft cbl2 packer 1.9.5-8
Microsoft cbl2 skopeo 1.14.2-9
Microsoft cbl2 keda 2.4.0-26
Microsoft cbl2 telegraf 1.29.4-8
Microsoft cbl2 cri-o 1.21.7-2
Microsoft cbl2 influxdb 2.6.1-20
Microsoft cbl2 cert-manager 1.11.2-14
Microsoft cbl2 containerized-data-importer 1.55.0-20
Microsoft cbl2 dcos-cli 1.2.0-19

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/gopkg.in/go-jose/go-jose.v2 to a version that resolves this vulnerability.

    Fixed in 2.6.3
  2. Upgrade

    Upgrade go/github.com/go-jose/go-jose/v3 to a version that resolves this vulnerability.

    Fixed in 3.0.3
  3. Upgrade

    Upgrade go/github.com/go-jose/go-jose/v4 to a version that resolves this vulnerability.

    Fixed in 4.0.1
  4. Upgrade

    Upgrade redhat/go-jose to a version that resolves this vulnerability.

    Fixed in 4.0.1
  5. Upgrade

    Upgrade redhat/go-jose to a version that resolves this vulnerability.

    Fixed in 3.0.3
  6. Upgrade

    Upgrade redhat/go-jose to a version that resolves this vulnerability.

    Fixed in 2.6.3
  7. Upgrade

    Upgrade github.com/go-jose/go-jose/v3 to a version that resolves this vulnerability.

    Fixed in 3.0.3Patch GHSA-c5q2-7r4c-mv6g
  8. Upgrade

    Upgrade github.com/go-jose/go-jose/v4 to a version that resolves this vulnerability.

    Fixed in 4.0.1Patch GHSA-c5q2-7r4c-mv6g
  9. Upgrade

    Upgrade gopkg.in/go-jose/go-jose.v2 to a version that resolves this vulnerability.

    Fixed in 2.6.3Patch GHSA-c5q2-7r4c-mv6g

Event History

Mar 7, 2024
Advisory Published
via GitHub·10:54 PM
Mar 9, 2024
CVE Published
via MITRE·12:54 AM
Data Sourced
via MITRE·12:54 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 AM
RemedyAffected Software
Mar 10, 2024
Data Sourced
via Red Hat·08:20 PM
DescriptionSeverityAffected Software
Apr 11, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Updated
via Microsoft·07:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2024-28180?

CVE-2024-28180 has a medium severity rating due to the potential for resource exhaustion.

2

How do I fix CVE-2024-28180?

To mitigate CVE-2024-28180, update to go-jose versions 2.6.3, 3.0.3, or 4.0.1.

3

What types of attacks are associated with CVE-2024-28180?

CVE-2024-28180 can be exploited through specially crafted JSON Web Encryption (JWE) tokens to cause excessive resource consumption.

4

Which software versions are affected by CVE-2024-28180?

CVE-2024-28180 affects go-jose versions prior to 2.6.3, 3.0.3, and 4.0.1.

5

What are the new limitations introduced by CVE-2024-28180?

CVE-2024-28180 adds limitations to JWE decompression, capping it at 250kB or 10 times the compressed size.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203