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

jose vulnerable to resource exhaustion via specifically crafted JWE with compressed plaintext

panva · jose

4.9MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivenode-joseUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical record ↗Source updated 11 Sept 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-28176 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjose: resource exhaustion
3 known affected

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

  • jose.src as a component of Red Hat Enterprise Linux 7
  • libjose as a component of Red Hat Enterprise Linux 7
  • libjose-devel as a component of Red Hat Enterprise Linux 7
Summary
Jose was found to have an uncontrolled resource consumption vulnerability. Under certain conditions, the user's environment can consume an unreasonable amount of CPU time or memory during JWE decryption operations, leading to a denial of service.
Remediation
For Red Hat Advanced Cluster Management for Kubernetes, see the following documentation, which will be updated shortly for this release: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html-single/install/index#installing
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-0938

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

jose is JavaScript module for JSON Object Signing and Encryption, providing support for JSON Web Tokens (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE), JSON Web Key (JWK), JSON Web Key Set (JWKS), and more. A vulnerability has been identified in the JSON Web Encryption (JWE) decryption interfaces, specifically related to the support for decompressing plaintext after its decryption. Under certain conditions it is possible to have the user's environment consume unreasonable amount of CPU time or memory during JWE Decryption operations. This issue has been patched in versions 2.0.7 and 4.15.5.

What

jose is JavaScript module for JSON Object Signing and Encryption, providing support for JSON Web Tokens (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE), JSON Web Key (JWK), JSON Web Key Set (JWKS), and more. A vulnerability has been identified in the JSON Web Encryption (JWE) decryption interfaces, specifically related to the support for decompressing plaintext after its decryption. Under certain conditions it is possible to have the user's environment consume unreasonable amount of CPU time or memory during JWE Decryption operations. This issue has been patched in versions 2.0.7 and 4.15.5.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

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

What

jose is JavaScript module for JSON Object Signing and Encryption, providing support for JSON Web Tokens (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE), JSON Web Key (JWK), JSON Web Key Set (JWKS), and more. A vulnerability has been identified in the JSON Web Encryption (JWE) decryption interfaces, specifically related to the support for decompressing plaintext after its decryption. Under certain conditions it is possible to have the user's environment consume unreasonable amount of CPU time or memory during JWE Decryption operations. This issue has been patched in versions 2.0.7 and 4.15.5.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation with elevated 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 → Uncontrolled Resource Consumption → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
High: elevated access 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-400

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

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:H/UI:N/S:U/C:N/I:N/A:H

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.PRHighPrivileges required: The attacker needs elevated or administrative 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.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkCWE-400
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-0767IBM App Connect Enterprise: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um beliebigen Programmcode auszuführen oder einen Denial-of-Service-Zustand zu verursachen.

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

rd?id=CVE-2024-2398 Référence CVE CVE-2024-25016 https://www.cve.org/CVERecord?id=CVE-2024-25016 Référence CVE CVE-2024-25629 https://www.cve.org/CVERecord?id=CVE-2024-25629 Référence CVE CVE-2024-25638 https://www.cve.org/CVERecord?id=CVE-2024-25638 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-27980 https://www.cve.org/CVERecord?id=CVE-2024-27980 Référence CVE CVE-2024-27982 https://www.cve.org/CVERecord?id=CVE-2024-27982 Référence CVE CVE-2024-27983 https://www.cve.org/CVERecord?id=CVE-2024-27983 Référence CVE CVE-2024-28176 https://www.cve.org/CVERecord?id=CVE-2024-28176 Référence CVE CVE-2024-28757 https://www.cve.org/CVERecord?id=CVE-2024-28757 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-28863 https://www.cve.org/CVERecord?id=CVE-2024-28863 Référence CVE CVE-2024-29025 https://www.cve.org/CVERecord?id=CVE-2024-29025 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-29857 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-22233 Référence CVE CVE-2024-22353 https://www.cve.org/CVERecord?id=CVE-2024-22353 Référence CVE CVE-2024-22361 https://www.cve.org/CVERecord?id=CVE-2024-22361 Référence CVE CVE-2024-25024 https://www.cve.org/CVERecord?id=CVE-2024-25024 Référence CVE CVE-2024-25062 https://www.cve.org/CVERecord?id=CVE-2024-25062 Référence CVE CVE-2024-25629 https://www.cve.org/CVERecord?id=CVE-2024-25629 Référence CVE CVE-2024-27267 https://www.cve.org/CVERecord?id=CVE-2024-27267 Référence CVE CVE-2024-27982 https://www.cve.org/CVERecord?id=CVE-2024-27982 Référence CVE CVE-2024-27983 https://www.cve.org/CVERecord?id=CVE-2024-27983 Référence CVE CVE-2024-28176 https://www.cve.org/CVERecord?id=CVE-2024-28176 Référence CVE CVE-2024-28182 https://www.cve.org/CVERecord?id=CVE-2024-28182 Référence CVE CVE-2024-28799 https://www.cve.org/CVERecord?id=CVE-2024-28799 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-29415 https://www.cve.org/CVERecord?id=CVE-2024-29415 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=CV

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

ord?id=CVE-2024-25023 Référence CVE CVE-2024-25026 https://www.cve.org/CVERecord?id=CVE-2024-25026 Référence CVE CVE-2024-25062 https://www.cve.org/CVERecord?id=CVE-2024-25062 Référence CVE CVE-2024-2511 https://www.cve.org/CVERecord?id=CVE-2024-2511 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-27088 https://www.cve.org/CVERecord?id=CVE-2024-27088 Référence CVE CVE-2024-27270 https://www.cve.org/CVERecord?id=CVE-2024-27270 Référence CVE CVE-2024-28102 https://www.cve.org/CVERecord?id=CVE-2024-28102 Référence CVE CVE-2024-28176 https://www.cve.org/CVERecord?id=CVE-2024-28176 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-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-28863 https://www.cve.org/CVERecord?id=CVE-2024-28863 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 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=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-029519jose project の jose 等複数ベンダの製品におけるリソースの枯渇に関する脆弱性

jose project の 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.
Patch available
Affected
Fixed
Action
For Red Hat Advanced Cluster Management for Kubernetes, see the following documentation, which will be updated shortly for this release: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html-single/install/index#installing
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-400 · Uncontrolled Resource Consumption

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-0938
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    jose.src as a component of Red Hat Enterprise Linux 7; libjose as a component of Red Hat Enterprise Linux 7; libjose-devel as a component of Red Hat Enterprise Linux 7 · Fixed: rhacm2/console-rhel8@sha256:617a8a449bd1c6e7eb91ce0173cca62c6a2939ad2456fca16ce0f78ba3993aad_arm64 as a component of Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8; rhacm2/console-rhel8@sha256:687b07dc606f789f165e10f9ddab2ab640bf8377cb230332204f689d5188b2b0_amd64 as a component of Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8; rhacm2/console-rhel8@sha256:92b8523d0d06eb27cff8ad4fc1c063a1b53860d5f27208dee4b4c23052d074b2_s390x as a component of Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8; rhacm2/console-rhel8@sha256:dbb19631867521b18db2284e9a8520ebc3082fe6e509b643f27ee3320f3ee1bb_ppc64le as a component of Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8; podman-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-4:4.9.4-5.1.rhaos4.16.el8.src as a component of Red Hat OpenShift Container Platform 4.16; podman-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-debugsource-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-debugsource-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-debugsource-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-debugsource-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-docker-4:4.9.4-5.1.rhaos4.16.el8.noarch as a component of Red Hat OpenShift Container Platform 4.16; podman-gvproxy-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-gvproxy-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-gvproxy-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-gvproxy-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; and 554 more
    After
    jose.src as a component of Red Hat Enterprise Linux 7; libjose as a component of Red Hat Enterprise Linux 7; libjose-devel as a component of Red Hat Enterprise Linux 7 · Fixed: rhacm2/console-rhel8@sha256:617a8a449bd1c6e7eb91ce0173cca62c6a2939ad2456fca16ce0f78ba3993aad_arm64 as a component of Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8; rhacm2/console-rhel8@sha256:687b07dc606f789f165e10f9ddab2ab640bf8377cb230332204f689d5188b2b0_amd64 as a component of Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8; rhacm2/console-rhel8@sha256:92b8523d0d06eb27cff8ad4fc1c063a1b53860d5f27208dee4b4c23052d074b2_s390x as a component of Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8; rhacm2/console-rhel8@sha256:dbb19631867521b18db2284e9a8520ebc3082fe6e509b643f27ee3320f3ee1bb_ppc64le as a component of Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8; podman-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-4:4.9.4-5.1.rhaos4.16.el8.src as a component of Red Hat OpenShift Container Platform 4.16; podman-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-catatonit-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-debuginfo-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-debugsource-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-debugsource-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-debugsource-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-debugsource-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; podman-docker-4:4.9.4-5.1.rhaos4.16.el8.noarch as a component of Red Hat OpenShift Container Platform 4.16; podman-gvproxy-4:4.9.4-5.1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.16; podman-gvproxy-4:4.9.4-5.1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.16; podman-gvproxy-4:4.9.4-5.1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.16; podman-gvproxy-4:4.9.4-5.1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.16; and 574 more
    Red Hat Product Security
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-28176 · cve.blacktree.nl