OpenShift Developer Tools and Services: Improper Limitation of a Pathname to a Restricted Directory
CVE-2024-1485 is a critical-severity improper limitation of a pathname to a restricted directory vulnerability in OpenShift Developer Tools and Services from Red Hat, with a CVSS 3.1 base score of 9.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, 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 0.94% chance of exploitation within 30 days, higher than 62% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Registry-support to 0.0.0-20240206 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- 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 | OpenShift Developer Tools and Services | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4 | Not specified in the record | Not stated |
| Devfile | Registry-support | before 0.0.0-20240206 | 0.0.0-20240206 |
| Red Hat | Openshift | 4.0 | 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
- NoneNo account or login is needed.
- 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
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.0 | High | CNA (redhat.com) |
| CVSS 3.1 | 9.3 | Critical | NVD |
Official description
A flaw was found in the decompression function of registry-support. This issue can be triggered if an unauthenticated remote attacker tricks a user into parsing a devfile which uses the `parent` or `plugin` keywords. This could download a malicious archive and cause the cleanup process to overwrite or delete files outside of the archive, which should not be allowed.
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: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/advisories/GHSA-84xv-jfrm-h4gmThird Party Advisory
Patches and release notes
Third-party and government advisories
- access.redhat.com/security/cve/CVE-2024-1485Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2264106Issue Tracking, Third Party Advisory
Other vulnerabilities in OpenShift Developer Tools and Services
- 8.5 High severity
- 8.1 High severity
- 7.3 High severity
- 7.5 High severity
- 8.1 High severity
- 7.5 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 8.0 High severity
- 7.8 High severity
- 7.2 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
Spotted an error? Tell us.