cve.bz

CVE-2022-27652 Incorrect Default Permissions

5.3 mediumEPSS 0.2%Fix available

Medium (5.3). EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/cri-o/cri-o 1.24.0.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-276 Incorrect Default Permissions
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-27652 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-27652?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-27652?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-27652 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
fedoraproject:fedora35
mobyproject:mobybefore 20.10.14
redhat:openshift_container_platform3.11
redhat:openshift_container_platform4.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4hj2-r2pm-3hc6Gogithub.com/cri-o/cri-o<1.24.01.24.0
GO-2022-0426Gogithub.com/cri-o/cri-o<1.24.01.24.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatopenshift:4.9::el7cri-o, cri-o-debuginfo0:1.22.5-7.rhaos4.9.git3dbcd3c.el7RHBA-2022:5433
Red Hatopenshift:4.9::el8cri-o, cri-o-debuginfo, cri-o-debugsource0:1.22.5-7.rhaos4.9.git3dbcd3c.el8RHBA-2022:5433
Red Hatopenshift:4.10::el8cri-o, cri-o-debuginfo, cri-o-debugsource0:1.23.2-8.rhaos4.10.git8ad5d25.el8RHSA-2022:1600
Red Hatopenshift:4.10::el8jenkins-2-plugins0:4.10.1650890594-1.el8RHSA-2022:1600

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This issue is related to the general vulnerability found in Moby (Docker Engine), which has been assigned CVE-2022-24769. After further investigation we came to the conclusion that this CVE has a very minimal impact on Red Hat OpenShift Container Platform.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 4.10cri-o-0:1.23.2-8.rhaos4.10.git8ad5d25.el8Fixed 2022-05-02RHSA-2022:1600
Red Hat OpenShift Container Platform 4.9cri-o-0:1.22.5-7.rhaos4.9.git3dbcd3c.el7Fixed 2022-07-05RHBA-2022:5433
Red Hat OpenShift Container Platform 3.11cri-oOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-27652.

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON