Incorrect Default Permissions Affecting cri-o package, versions <0:1.22.5-7.rhaos4.9.git3dbcd3c.el7


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (15th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Incorrect Default Permissions vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-CRIO-5353565
  • published26 Mar 2023
  • disclosed30 Mar 2022

Introduced: 30 Mar 2022

CVE-2022-27652  (opens in a new tab)
CWE-276  (opens in a new tab)

How to fix?

Upgrade RHEL:7 cri-o to version 0:1.22.5-7.rhaos4.9.git3dbcd3c.el7 or higher.
This issue was patched in RHBA-2022:5433.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cri-o package and not the cri-o package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions. A vulnerability was found in Moby (Docker Engine) where containers 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.

CVSS Scores

version 3.1