What is CVE-2024-9676?A medium-severity flaw in Openshift Container Platform, explained.
CVE-2024-9676 is a medium-severity flaw (CVSS 6.5) in Openshift Container Platform from Red Hat, published on 15 October 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.3%. If you run an affected version, plan in the vendor’s fix.
Published 15 October 2024. Record last updated 17 June 2026. We keep this page's data up to date.
What is CVE-2024-9676? In plain terms.
It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline.
A vulnerability was found in Podman, Buildah, and CRI-O. A symlink traversal vulnerability in the containers/storage library can cause Podman, Buildah, and CRI-O to hang and result in a denial of service via OOM kill when running a malicious image using an automatically assigned user namespace (`--userns=auto` in Podman and Buildah). The containers/storage library will read /etc/passwd inside the container, but does not properly validate if that file is a symlink, which can be used to cause the library to read an arbitrary file on the host.
What kind of flaw is it?
- CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is CVE-2024-9676 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.3%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2024-9676 scores 28. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2024-9676 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2024-9676? 15 products.
The published record lists 15 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Application
Openshift Container Platform
by Red Hat
Affected versions4.124.134.144.154.164.17 - Application
Openshift Container Platform for Arm64
by Red Hat
Affected versions4.124.134.144.154.16 - Application
Openshift Container Platform for Ibm Z
by Red Hat
Affected versions4.124.134.144.154.16 - Application
Openshift Container Platform for Linuxone
by Red Hat
Affected versions4.124.134.144.154.16 - Application
Openshift Container Platform for Power
by Red Hat
Affected versions4.124.134.144.154.16 - Operating system
Enterprise Linux
by Red Hat
Affected versions9.0 - Operating system
Enterprise Linux Eus
by Red Hat
Affected versions9.4 - Operating system
Enterprise Linux for Arm 64
by Red Hat
Affected versions9.0_aarch64 - Operating system
Enterprise Linux for Arm 64 Eus
by Red Hat
Affected versions9.4_aarch64
How do I fix CVE-2024-9676? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2024-9676 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A vulnerability was found in Podman, Buildah, and CRI-O. A symlink traversal vulnerability in the containers/storage library can cause Podman, Buildah, and C...
- Matched to
- Openshift Container Platform on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2024-9676 is a medium-severity flaw in Openshift Container Platform from Red Hat, published on 15 October 2024. It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 6.5 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2024-9676 is 28 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.3%. That can change at any time, which is why we keep watching.
For Openshift Container Platform from Red Hat: 4.12, 4.13, 4.14, 4.15, 4.16, 4.17. The record lists 15 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.