github.com/containerd/containerd
Affected
- introduced
0, fixed1.5.18(semver)
Fixed versions
1.5.18
Fix
- Fixed version
1.5.18go get github.com/containerd/[email protected]
Advisory
Also known as: CVE-2023-25173, GO-2023-1574
Supplementary groups are not set up properly in github.com/containerd/containerd
Impact
A bug was found in containerd where supplementary groups are not set up properly inside a container. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container.
Downstream applications that use the containerd client library may be affected as well.
Patches
This bug has been fixed in containerd v1.6.18 and v.1.5.18. Users should update to these versions and recreate containers to resolve this issue. Users who rely on a downstream application that uses containerd's client library should check that application for a separate advisory and instructions.
Workarounds
Ensure that the "USER $USERNAME" Dockerfile instruction is not used. Instead, set the container entrypoint to a value similar to ENTRYPOINT ["su", "-", "user"] to allow su to properly set up supplementary groups.
References
Note that CVE IDs apply to a particular implementation, even if an issue is common.
For more information
If you have any questions or comments about this advisory:
To report a security issue in containerd:
Medium Basis: The source's own band: MODERATE
0, fixed 1.5.18 (semver)1.5.18
1.5.18go get github.com/containerd/[email protected]1.6.0, fixed 1.6.18 (semver)1.6.18
1.6.18go get github.com/containerd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0