Bug 1198194 - (CVE-2022-27652) VUL-1: CVE-2022-27652: cri-o: Default inheritable capabilities for linux container should be empty
(CVE-2022-27652)
VUL-1: CVE-2022-27652: cri-o: Default inheritable capabilities for linux cont...
Status: NEW
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P4 - Low : Normal
: ---
Assigned To: Valentin Rothberg
Security Team bot
https://smash.suse.de/issue/327767/
CVSSv3.1:SUSE:CVE-2022-27652:4.9:(AV:...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-04-07 11:31 UTC by Hu
Modified: 2022-04-07 12:15 UTC (History)
1 user (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hu 2022-04-07 11:31:33 UTC
rh#2066839

A bug was found in Moby (Docker Engine) where containers were incorrectly started with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted.

This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set.

Patches
This bug has been fixed in Moby (Docker Engine) 20.10.14. Users should update to this version as soon as possible. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset.

This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. Refer to capabilities(7) for a description of how capabilities work. Note that permitted file capabilities continue to allow for privileges to be raised up to the container's bounding set and that processes may add capabilities to their own inheritable set up to the container's bounding set per the rules described in the manual page. In all cases the container's bounding set provides an upper bound on the capabilities that can be assumed and provides for the container security sandbox.

Workarounds
The entrypoint of a container can be modified to use a utility like capsh(1) to drop inheritable capabilities prior to the primary process starting.

References:
https://bugzilla.redhat.com/show_bug.cgi?id=2066839
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-27652
Comment 1 Hu 2022-04-07 11:34:19 UTC
Affected:
- SUSE:SLE-15-SP1:Update:Products:CASP40:Update/cri-o
- openSUSE:Factory/cri-o

I think upstream is working on a fix here:
- for main branch: https://github.com/cri-o/cri-o/pull/5769
- for release-1.23 branch: https://github.com/cri-o/cri-o/pull/5770