DescriptionDocker Engine 1.12.2 enabled ambient capabilities with misconfigured capability policies. This allowed malicious images to bypass user permissions to access files within the container filesystem or mounted volumes.
SourceCVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus (PTS)buster, buster (security)18.09.1+dfsg1-7.1+deb10u3fixed
sid, trixie20.10.25+dfsg1-3fixed
runc (PTS)buster1.0.0~rc6+dfsg1-3fixed
buster (security)1.0.0~rc6+dfsg1-3+deb10u3fixed
bullseye (security), bullseye1.0.0~rc93+ds1-5+deb11u3fixed
bookworm, bookworm (security)1.1.5+ds1-1+deb12u1fixed
sid, trixie1.1.12+ds1-2fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
docker.iosource(unstable)(not affected)
runcsource(unstable)(not affected)


- <not-affected> (Not built from/with a runc with "ambient capabilities")
- runc <not-affected> ("ambient capabilities" introduced later, cf bug #853240)
docker: (1.12.3)
runc: not directly affected but will need to be updated to include new runc version
runc: "ambient capabilities" functionality added upstream with
and later changes.
The actual fix seem to be to revert the commit which introduced ambient capabilities
in runc.

Search for package or bug name: Reporting problems