Red Hat OpenShift Container Platform 4.12: Improper Limitation of a Pathname to a Restricted Directory
CVE-2024-5154 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Red Hat OpenShift Container Platform 4.12 from Red Hat, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, but only if a user takes part, for example by opening a link or file. There is no confirmed exploitation so far. EPSS estimates a 1.24% chance of exploitation within 30 days, higher than 70% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat OpenShift Container Platform 4.12 you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on access.redhat.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Red Hat OpenShift Container Platform 4.12 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.13 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.14 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.15 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.16 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.17 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 3.11 | Not specified in the record | Not stated |
| Kubernetes | Cri-o | 1.28.6; 1.29.4; 1.30.0 | Not stated |
| Red Hat | Openshift Container Platform | 3.11; 4.0; 4.12; 4.13; 4.14; 4.15 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N. Scored by CNA (redhat.com).
Official description
A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via directory traversal (“../“). This flaw allows the container to read and write to arbitrary files on the host system.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
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.
How developers prevent this class of flaw
- 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 entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
Other vulnerabilities in Red Hat OpenShift Container Platform 4.12
- 7.7 High severity
- 7.7 High severity
- 7.5 High severity
- 9.3 Critical severity
- 7.4 High severity
- 7.5 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 8.1 High severity
- 9.1 Critical severity
- 8.8 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.1 Critical severity
Spotted an error? Tell us.