CyberSecBulletin
CVE-2022-27649NVD status: Modified

podman: Incorrect Default Permissions

Published Updated By the CyberSecBulletin desk

CVE-2022-27649 is a high-severity incorrect default permissions vulnerability in podman, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected podman versions: Affects all versions before v4.0.3, Fixed in - v4.0.3. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.43% chance of exploitation within 30 days, higher than 73% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of podman you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on github.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
PodmanpodmanAffects all versions before v4.0.3, Fixed in - v4.0.3Not stated
Red HatDeveloper Tools1.0Not stated
Red HatOpenshift Container Platform4.0Not stated
Red HatEnterprise Linux8.0; 8.6Not stated
Red HatEnterprise Linux EUS8.4; 8.6Not stated
Red HatEnterprise Linux For IBM Z Systems8.0; 8.6Not stated
Red HatEnterprise Linux For IBM Z Systems EUS8.4; 8.6Not stated
Red HatEnterprise Linux For Power Little Endian8.0Not stated
Red HatEnterprise Linux For Power Little Endian EUS8.4Not stated
Red HatEnterprise Linux Server AUS8.4; 8.6Not stated
Red HatEnterprise Linux Server For Power Little Endian Update Services For SAP Solutions8.4; 8.6Not stated
Red HatEnterprise Linux Server TUS8.4; 8.6Not stated
Red HatEnterprise Linux Server Update Services For SAP Solutions8.4; 8.6Not stated
Fedora ProjectFedora34; 35; 36Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighNVD
CVSS 2.06.0MediumNVD

Official description

A flaw was found in Podman, where containers were started incorrectly 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Default Permissions

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

How developers prevent this class of flaw

  • The architecture needs to access and modification attributes for files to only those users who actually require those actions.
  • 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.

More Incorrect Default Permissions vulnerabilities (CWE-276)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in podman

All podman vulnerabilities

Recent Incorrect Default Permissions vulnerabilities

Spotted an error? Tell us.