libcontainer
Affected
- introduced
0, fixed0.5.3(semver)
Fixed versions
0.5.3
Fix
- Fixed version
0.5.3cargo update -p libcontainer --precise 0.5.3
Advisory
Also known as: CVE-2025-27612
Libcontainer is affected by capabilities elevation similar to GHSA-f3fp-gc8g-vw66
Impact
In libcontainer, while creating a tenant container, the tenant builder accepts a list of capabilities to be added in the spec of tenant container. Code can be seen here . The logic here adds the given capabilities to all capabilities of main container if present in spec, otherwise simply set provided capabilities as capabilities of the tenant container.
However, GHSA-f3fp-gc8g-vw66 was opened on runc mentioning that setting inherited caps in any case for tenant container can lead to elevation of capabilities. For this, they added a fix here where they never set new inherited caps on tenant, and set ambient caps only if original container had inherited caps.
Similarly crun never sets inherited caps as can be seen here.
> [!NOTE]
This does not affect youki binary itself, as the exec implementation is partially broken and does not pass on the user-provided caps to tenant containers, this is only applicable if you are using libcontainer directly and using the tenant builder.
Workarounds
References
Medium Basis: The source's own band: MODERATE
0, fixed 0.5.3 (semver)0.5.3
0.5.3cargo update -p libcontainer --precise 0.5.3Fix 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