Skip to content

Podman's default inheritable capabilities for linux container not empty

High severity GitHub Reviewed Published Apr 1, 2022 in podman-container-tools/podman • Updated Jan 27, 2023

Package

gomod github.com/containers/podman/v4 (Go)

Affected versions

< 4.0.3

Patched versions

4.0.3

Description

A bug was found in Podman where containers were created 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).

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.

References

@giuseppe giuseppe published to podman-container-tools/podman Apr 1, 2022
Published to the GitHub Advisory Database Apr 1, 2022
Reviewed Apr 1, 2022
Published by the National Vulnerability Database Apr 4, 2022
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(70th percentile)

Weaknesses

Incorrect Default Permissions

During installation, installed file permissions are set to allow anyone to modify those files. Learn more on MITRE.

CVE ID

CVE-2022-27649

GHSA ID

GHSA-qvf8-p83w-v58j

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.