BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-28180High confidence

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

go-jose · go-jose

Official source article: GitHub GHSA-C5Q2-7R4C-MV6G ↗. Check the applicable product and release in the original source.

4.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 1.96% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs go-jose go-jose and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

10 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communitybuildahVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.35.4-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communitybuildahVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.35.4-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.21v3.21 · communitybuildahVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.35.4-r0Alpine Security Database ↗Source updated 19 Aug 2026
Debian trixietrixie · sourcegolang-github-go-jose-go-joseVendor fix publishedDebian records a fixed source-package version for this release.4.0.1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · sourcegolang-gopkg-square-go-jose.v2Vendor fix publishedDebian records a fixed source-package version for this release.2.6.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcegolang-gopkg-square-go-jose.v2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcegolang-github-go-jose-go-joseVendor fix publishedDebian records a fixed source-package version for this release.4.0.1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcegolang-gopkg-square-go-jose.v2Vendor fix publishedDebian records a fixed source-package version for this release.2.6.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcegolang-github-go-jose-go-joseVendor fix publishedDebian records a fixed source-package version for this release.4.0.1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcegolang-gopkg-square-go-jose.v2Vendor fix publishedDebian records a fixed source-package version for this release.2.6.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/go-jose/go-jose/v3SEMVER: introduced 0; fixed 3.0.33.0.3OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/go-jose/go-jose/v4SEMVER: introduced 0; fixed 4.0.14.0.1OSV record ↗aggregator derived · 10 Sep 2026
Gogopkg.in/go-jose/go-jose.v2SEMVER: introduced 0; fixed 2.6.32.6.3OSV record ↗aggregator derived · 10 Sep 2026
Gogopkg.in/square/go-jose.v2SEMVER: introduced 0; last affected 2.6.0Not statedOSV record ↗aggregator derived · 10 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-28180 · CSAF 2.0 · revision 69 · interimSUSE Product Security TeamCVE-2024-28180
47 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • buildah as component of SLES-LTSS-TERADATA 15 SP2
  • containerized-data-importer as component of SLES-LTSS-TERADATA 15 SP2
  • podman as component of SLES-LTSS-TERADATA 15 SP2
  • buildah as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • podman as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • podman-cni-config as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • buildah as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • containerized-data-importer as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • containerized-data-importer-manifests as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • podman as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • podman-cni-config as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • containerized-data-importer as component of SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-0896

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Handling of Highly Compressed Data (Data Amplification) → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-409 ↗

CWE-409: Improper Handling of Highly Compressed Data (Data Amplification). The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-409
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-1474Red Hat OpenShift Container Platform: Mehrere Schwachstellen

Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder Daten zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2024-2035Red Hat OpenShift: Mehrere Schwachstellen ermöglichen Manipulation von Dateien und Denial of Service

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Dateien zu manipulieren und um einen Denial of Service zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2024-0947Red Hat OpenShift: Mehrere Schwachstellen

Ein entfernter authentifizierter Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240313Security Bulletin 13 Mar 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 13 Mar 2024, published on 13 March 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0112Multiples vulnérabilités dans les produits VMware

adcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36911 Référence CVE CVE-2016-1000027 https://www.cve.org/CVERecord?id=CVE-2016-1000027 Référence CVE CVE-2022-29526 https://www.cve.org/CVERecord?id=CVE-2022-29526 Référence CVE CVE-2022-49390 https://www.cve.org/CVERecord?id=CVE-2022-49390 Référence CVE CVE-2023-34231 https://www.cve.org/CVERecord?id=CVE-2023-34231 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2024-21510 https://www.cve.org/CVERecord?id=CVE-2024-21510 Référence CVE CVE-2024-23337 https://www.cve.org/CVERecord?id=CVE-2024-23337 Référence CVE CVE-2024-28180 https://www.cve.org/CVERecord?id=CVE-2024-28180 Référence CVE CVE-2024-38816 https://www.cve.org/CVERecord?id=CVE-2024-38816 Référence CVE CVE-2024-38819 https://www.cve.org/CVERecord?id=CVE-2024-38819 Référence CVE CVE-2024-38820 https://www.cve.org/CVERecord?id=CVE-2024-38820 Référence CVE CVE-2024-38828 https://www.cve.org/CVERecord?id=CVE-2024-38828 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-47220 https://www.cve.org/CVERecord?id=CVE-2024-47220 Référence CVE CVE-2024-47691 https://www.cve.org/CVERecord?id=CVE-2024-47691 Référence CVE CVE-2024-50067 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0756Multiples vulnérabilités dans les produits VMware

rd?id=CVE-2024-2511 Référence CVE CVE-2024-25260 https://www.cve.org/CVERecord?id=CVE-2024-25260 Référence CVE CVE-2024-26458 https://www.cve.org/CVERecord?id=CVE-2024-26458 Référence CVE CVE-2024-26461 https://www.cve.org/CVERecord?id=CVE-2024-26461 Référence CVE CVE-2024-26462 https://www.cve.org/CVERecord?id=CVE-2024-26462 Référence CVE CVE-2024-26686 https://www.cve.org/CVERecord?id=CVE-2024-26686 Référence CVE CVE-2024-26739 https://www.cve.org/CVERecord?id=CVE-2024-26739 Référence CVE CVE-2024-27402 https://www.cve.org/CVERecord?id=CVE-2024-27402 Référence CVE CVE-2024-28085 https://www.cve.org/CVERecord?id=CVE-2024-28085 Référence CVE CVE-2024-28180 https://www.cve.org/CVERecord?id=CVE-2024-28180 Référence CVE CVE-2024-28182 https://www.cve.org/CVERecord?id=CVE-2024-28182 Référence CVE CVE-2024-28834 https://www.cve.org/CVERecord?id=CVE-2024-28834 Référence CVE CVE-2024-28835 https://www.cve.org/CVERecord?id=CVE-2024-28835 Référence CVE CVE-2024-2961 https://www.cve.org/CVERecord?id=CVE-2024-2961 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-30171 https://www.cve.org/CVERecord?id=CVE-2024-30171 Référence CVE CVE-2024-30172 https://www.cve.org/CVERecord?id=CVE-2024-30172 Référence CVE CVE-2024-31047 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0622Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2024-24787 Référence CVE CVE-2024-24789 https://www.cve.org/CVERecord?id=CVE-2024-24789 Référence CVE CVE-2024-24790 https://www.cve.org/CVERecord?id=CVE-2024-24790 Référence CVE CVE-2024-24791 https://www.cve.org/CVERecord?id=CVE-2024-24791 Référence CVE CVE-2024-2511 https://www.cve.org/CVERecord?id=CVE-2024-2511 Référence CVE CVE-2024-25710 https://www.cve.org/CVERecord?id=CVE-2024-25710 Référence CVE CVE-2024-26308 https://www.cve.org/CVERecord?id=CVE-2024-26308 Référence CVE CVE-2024-27282 https://www.cve.org/CVERecord?id=CVE-2024-27282 Référence CVE CVE-2024-28085 https://www.cve.org/CVERecord?id=CVE-2024-28085 Référence CVE CVE-2024-28180 https://www.cve.org/CVERecord?id=CVE-2024-28180 Référence CVE CVE-2024-29018 https://www.cve.org/CVERecord?id=CVE-2024-29018 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-29902 https://www.cve.org/CVERecord?id=CVE-2024-29902 Référence CVE CVE-2024-29903 https://www.cve.org/CVERecord?id=CVE-2024-29903 Référence CVE CVE-2024-30171 https://www.cve.org/CVERecord?id=CVE-2024-30171 Référence CVE CVE-2024-30172 https://www.cve.org/CVERecord?id=CVE-2024-30172 Référence CVE CVE-2024-3219 https://www.cve.org/CVERecord?id=CVE-2024-3219 Référence CVE CVE-2024-34155 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0473Multiples vulnérabilités dans les produits Splunk

De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, une injection de code indirecte à distance (XSS) et un contournement de la politique de sécurité.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0878Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2023-45285 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-45803 https://www.cve.org/CVERecord?id=CVE-2023-45803 Référence CVE CVE-2023-47108 https://www.cve.org/CVERecord?id=CVE-2023-47108 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2023-50658 https://www.cve.org/CVERecord?id=CVE-2023-50658 Référence CVE CVE-2024-24557 https://www.cve.org/CVERecord?id=CVE-2024-24557 Référence CVE CVE-2024-24786 https://www.cve.org/CVERecord?id=CVE-2024-24786 Référence CVE CVE-2024-24790 https://www.cve.org/CVERecord?id=CVE-2024-24790 Référence CVE CVE-2024-28180 https://www.cve.org/CVERecord?id=CVE-2024-28180 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-37891 https://www.cve.org/CVERecord?id=CVE-2024-37891 Référence CVE CVE-2024-45731 https://www.cve.org/CVERecord?id=CVE-2024-45731 Référence CVE CVE-2024-45732 https://www.cve.org/CVERecord?id=CVE-2024-45732 Référence CVE CVE-2024-45733 https://www.cve.org/CVERecord?id=CVE-2024-45733 Référence CVE CVE-2024-45734 https://www.cve.org/CVERecord?id=CVE-2024-45734 Référence CVE CVE-2024-45735 https://www.cve.org/CVERecord?id=CVE-2024-45735 Référence CVE CVE-2024-45736 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0741Multiples vulnérabilités dans Juniper Secure Analytics

d?id=CVE-2024-26982 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-27014 https://www.cve.org/CVERecord?id=CVE-2024-27014 Référence CVE CVE-2024-27048 https://www.cve.org/CVERecord?id=CVE-2024-27048 Référence CVE CVE-2024-27052 https://www.cve.org/CVERecord?id=CVE-2024-27052 Référence CVE CVE-2024-27056 https://www.cve.org/CVERecord?id=CVE-2024-27056 Référence CVE CVE-2024-27059 https://www.cve.org/CVERecord?id=CVE-2024-27059 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-28180 https://www.cve.org/CVERecord?id=CVE-2024-28180 Référence CVE CVE-2024-28182 https://www.cve.org/CVERecord?id=CVE-2024-28182 Référence CVE CVE-2024-28834 https://www.cve.org/CVERecord?id=CVE-2024-28834 Référence CVE CVE-2024-2961 https://www.cve.org/CVERecord?id=CVE-2024-2961 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-30171 https://www.cve.org/CVERecord?id=CVE-2024-30171 Référence CVE CVE-2024-30172 https://www.cve.org/CVERecord?id=CVE-2024-30172 Référence CVE CVE-2024-3019 https://www.cve.org/CVERecord?id=CVE-2024-3019 Référence CVE CVE-2024-32002 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0646Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-26934 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=CVE-2024-26973 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-27014 https://www.cve.org/CVERecord?id=CVE-2024-27014 Référence CVE CVE-2024-27048 https://www.cve.org/CVERecord?id=CVE-2024-27048 Référence CVE CVE-2024-27052 https://www.cve.org/CVERecord?id=CVE-2024-27052 Référence CVE CVE-2024-27056 https://www.cve.org/CVERecord?id=CVE-2024-27056 Référence CVE CVE-2024-27059 https://www.cve.org/CVERecord?id=CVE-2024-27059 Référence CVE CVE-2024-28180 https://www.cve.org/CVERecord?id=CVE-2024-28180 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-29415 https://www.cve.org/CVERecord?id=CVE-2024-29415 Référence CVE CVE-2024-32002 https://www.cve.org/CVERecord?id=CVE-2024-32002 Référence CVE CVE-2024-32004 https://www.cve.org/CVERecord?id=CVE-2024-32004 Référence CVE CVE-2024-32020 https://www.cve.org/CVERecord?id=CVE-2024-32020 Référence CVE CVE-2024-32021 https://www.cve.org/CVERecord?id=CVE-2024-32021 Référence CVE CVE-2024-32465 https://www.cve.org/CVERecord?id=CVE-2024-32465 Référence CVE CVE-2024-32487 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0514Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-23082 Référence CVE CVE-2024-23672 https://www.cve.org/CVERecord?id=CVE-2024-23672 Référence CVE CVE-2024-23807 https://www.cve.org/CVERecord?id=CVE-2024-23807 Référence CVE CVE-2024-24549 https://www.cve.org/CVERecord?id=CVE-2024-24549 Référence CVE CVE-2024-24557 https://www.cve.org/CVERecord?id=CVE-2024-24557 Référence CVE CVE-2024-24786 https://www.cve.org/CVERecord?id=CVE-2024-24786 Référence CVE CVE-2024-25026 https://www.cve.org/CVERecord?id=CVE-2024-25026 Référence CVE CVE-2024-27289 https://www.cve.org/CVERecord?id=CVE-2024-27289 Référence CVE CVE-2024-27306 https://www.cve.org/CVERecord?id=CVE-2024-27306 Référence CVE CVE-2024-28180 https://www.cve.org/CVERecord?id=CVE-2024-28180 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-29131 https://www.cve.org/CVERecord?id=CVE-2024-29131 Référence CVE CVE-2024-29133 https://www.cve.org/CVERecord?id=CVE-2024-29133 Référence CVE CVE-2024-29180 https://www.cve.org/CVERecord?id=CVE-2024-29180 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-30171 https://www.cve.org/CVERecord?id=CVE-2024-30171 Référence CVE CVE-2024-30172 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-029484Go JOSE project の Go JOSE 等複数ベンダの製品における高圧縮データの処理 (データ増幅)に関する脆弱性

Go JOSE project の Go JOSE 等複数ベンダの製品には、高圧縮データの処理 (データ増幅)に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 9 Mar 2024 · Last source change 13 Feb 2025, 17:47 UTC · CWE-409 · Improper Handling of Highly Compressed Data (Data Amplification)

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-0896
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-0896↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference · GitHub GHSA-C5Q2-7R4C-MV6G↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-28180 · cve.blacktree.nl