Red Hat OpenShift Container Platform 4.12: Incorrect Permission Assignment for Critical Resource
CVE-2024-45497 is a high-severity incorrect permission assignment for critical resource vulnerability in Red Hat OpenShift Container Platform 4.12 from Red Hat, with a CVSS 3.1 base score of 7.6 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.58% chance of exploitation within 30 days, which is low compared with other 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.
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.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 OpenShift Container Platform 4.18 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.19 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4.20 | Not specified in the record | Not stated |
| Red Hat | Red Hat Fuse 7 | Not specified in the record | 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
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H. Scored by CNA (redhat.com).
Official description
A flaw was found in the OpenShift build process, where the docker-build container is configured with a hostPath volume mount that maps the node's /var/lib/kubelet/config.json file into the build pod. This file contains sensitive credentials necessary for pulling images from private repositories. The mount is not read-only, which allows the attacker to overwrite it. By modifying the config.json file, the attacker can cause a denial of service by preventing the node from pulling new images and potentially exfiltrating sensitive secrets. This flaw impacts the availability of services dependent on image pulls and exposes sensitive information to unauthorized parties.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
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
Other references
- access.redhat.com/errata/RHSA-2025:10270
- access.redhat.com/errata/RHSA-2025:10294
- access.redhat.com/errata/RHSA-2025:10747
- access.redhat.com/errata/RHSA-2025:9269
- access.redhat.com/errata/RHSA-2025:9278
- access.redhat.com/errata/RHSA-2025:9562
- access.redhat.com/errata/RHSA-2025:9759
- access.redhat.com/errata/RHSA-2025:9765
- access.redhat.com/security/cve/CVE-2024-45497
- bugzilla.redhat.com/show_bug.cgi?id=2308673
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 Incorrect Permission Assignment for Critical Resource vulnerabilities
- 7.3 High severity
- 7.1 High severity
- 9.8 Critical severity
- 7.8 High severity
- 8.1 High severity
- 7.1 High severity
Spotted an error? Tell us.