CVE Vulnerabilities

CVE-2022-27651

Incorrect Default Permissions

Published: Apr 04, 2022 | Modified: Nov 07, 2023
CVSS 3.x
6.8
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
CVSS 2.x
4.9 MEDIUM
AV:N/AC:M/Au:S/C:P/I:P/A:N
RedHat/V2
RedHat/V3
4.8 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Ubuntu
MEDIUM

A flaw was found in buildah where containers were incorrectly started with non-empty default permissions. A bug was found in Moby (Docker Engine) where containers were incorrectly started with non-empty inheritable Linux process capabilities, enabling an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs. This has the potential to impact confidentiality and integrity.

Weakness

During installation, installed file permissions are set to allow anyone to modify those files.

Affected Software

Name Vendor Start Version End Version
Buildah Buildah_project * 1.25.0 (excluding)
Red Hat Enterprise Linux 8 RedHat container-tools:3.0-8050020220411083214.e34216c9 *
Red Hat Enterprise Linux 8 RedHat container-tools:2.0-8050020220411114323.e34216c9 *
Red Hat Enterprise Linux 8 RedHat container-tools:rhel8-8060020220401155929.2e213529 *
Red Hat Enterprise Linux 8.2 Extended Update Support RedHat container-tools:2.0-8020020220420173758.28c38760 *
Red Hat Enterprise Linux 8.4 Extended Update Support RedHat container-tools:2.0-8040020220411112506.c0c392d5 *
Red Hat Enterprise Linux 8.4 Extended Update Support RedHat container-tools:3.0-8040020220419093313.c0c392d5 *
Golang-github-containers-buildah Ubuntu impish *
Golang-github-containers-buildah Ubuntu kinetic *
Golang-github-containers-buildah Ubuntu lunar *
Golang-github-containers-buildah Ubuntu trusty *
Golang-github-containers-buildah Ubuntu xenial *

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References