CVE-2022-27650: High severity con0217 project con0217 vulnerability

Published Mar 22, 2022
·
Updated

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.

Other sources

A flaw was found in crun where containers were incorrectly started with non-empty default permissions. A vulnerability was found in Moby (Docker Engine) where containers were started incorrectly with non-empty inheritable Linux process capabilities. This flaw allows an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs.

Affected Software

5 affected componentsFixes available
redhat/crun<1.4.4
1.4.4
Crun Project Crun<1.4.4
Fedoraproject Fedora=34
redhat OpenShift Container Platform=4.0
redhat Enterprise Linux=8.0

Remediation

Information

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

Event History

Mar 30, 2022
CVE Published
12:00 PM
Data Sourced
12:00 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 4, 2022
CVE Published
via MITRE·07:45 PM
Data Sourced
via MITRE·07:45 PM
DescriptionWeakness

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID for this flaw in crun?

The vulnerability ID for this flaw in crun is CVE-2022-27650.

2

What is the severity of CVE-2022-27650?

The severity of CVE-2022-27650 is high with a severity value of 7.5.

3

Which software is affected by CVE-2022-27650?

The software affected by CVE-2022-27650 includes crun, Moby (Docker Engine), Fedora, Redhat Openshift Container Platform, and Redhat Enterprise Linux.

4

How can I fix CVE-2022-27650 in crun?

To fix CVE-2022-27650 in crun, update to version 1.4.4 or higher.

5

Where can I find more information about CVE-2022-27650?

You can find more information about CVE-2022-27650 in the following references: [CVE.org](https://www.cve.org/CVERecord?id=CVE-2022-27650), [NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-27650), [GitHub Security Advisories](https://github.com/containers/crun/security/advisories/GHSA-wr4f-w546-m398), [Red Hat Bugzilla](https://bugzilla.redhat.com/show_bug.cgi?id=2066845), and [Red Hat Security Advisory](https://access.redhat.com/errata/RHSA-2022:1762).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203