CVE-2024-5154VulnerabilityPublished 17 Jul 2024Updated 31 Oct 2026

Red Hat Security Advisory: OpenShift Container Platform 4.13.45 packages and security update

Affects Red HatSource GCVE Database

Authoritative record:CVE-2024-5154· High 8.1

Not known to be exploited · CVSS 8.1 High · fixed in Red Hat OpenShift Container Platform 4.12 package updates : patch Red Hat cri-o soon.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	8.1

EPSS: 1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.30.1, 1.29.5, 1.28.7

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade cri-o to 1.30.1, 1.29.5 or 1.28.7.

Affected software

Product	Affected	Fixed in
cri-o	Affected >=1.30.0 <1.30.1	Fixed in 1.30.1
cri-o	Affected >=1.29.4 <1.29.5	Fixed in 1.29.5
cri-o	Affected >=1.28.6 <1.28.7	Fixed in 1.28.7
GitHubcri-o/cri-o`pkg:github/cri-o/cri-o`Other threats	Affected =1.28.6 =1.29.4 =1.30.0	Fixed in–
GitHubcri-o`pkg:github/cri-o`Other threats	Affected >=1.30.0 <1.30.1 >=1.29.4 <1.29.5 >=1.28.6 <1.28.7	Fixed in 1.30.1 1.29.5 1.28.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated RPM packages and container images in OpenShift Container Platform 4.13.45 that fix this vulnerability. Upgrades can be performed using the OpenShift CLI (oc) or web console following the official upgrade documentation. No additional mitigation steps are indicated beyond applying the official update.

Description

Red Hat OpenShift Container Platform 4.13.45 includes a security update addressing CVE-2024-5154, a vulnerability in cri-o where a malicious container can create a symbolic link on the host. This issue could allow containerized workloads to affect the host filesystem via symlink creation. Red Hat has released updated RPM packages and container images to fix this vulnerability. Users of OpenShift Container Platform 4.13 are advised to upgrade to these updated packages and images through the official release channels.

Impact

The vulnerability allows a malicious container to create symbolic links on the host, which could lead to unauthorized access or modification of host filesystem resources. This poses a security risk in containerized environments by potentially breaking container isolation boundaries. The severity is rated as Important (high) by Red Hat, indicating a significant security impact but no confirmed exploitation in the wild has been reported.

Summary

CVE-2024-5154 is a security vulnerability in the cri-o component of Red Hat OpenShift Container Platform 4.13. A malicious container could exploit this flaw to create symbolic links on the host system, potentially leading to unauthorized filesystem modifications or other impacts related to symlink manipulation. Red Hat has issued updated packages in OpenShift Container Platform 4.13.45 to remediate this issue. The advisory recommends upgrading to these updated packages and container images. The vulnerability is rated as having an Important security impact by Red Hat Product Security.

CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Oct 2026, 18:09 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats