dbcve.org
Cri OApplication · Kubernetes

CVE-2022-3466

MEDIUM · 5.3 CVSS v3.1 Published 2023-09-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The version of cri-o as released for Red Hat OpenShift Container Platform 4.9.48, 4.10.31, and 4.11.6 via RHBA-2022:6316, RHBA-2022:6257, and RHBA-2022:6658, respectively, included an incorrect version of cri-o missing the fix for CVE-2022-27652, which was previously fixed in OCP 4.9.41 and 4.10.12 via RHBA-2022:5433 and RHSA-2022:1600. This issue could allow an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs. For more details, see https://access.redhat.com/security/cve/CVE-2022-27652.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The cri-o container runtime in specific Red Hat OpenShift Container Platform versions (4.9.48, 4.10.31, 4.11.6) was shipped without the fix for CVE-2022-27652, a regression from earlier patched versions. This vulnerability allows attackers with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2) system calls, enabling privilege escalation.

MitigationUpgrade OpenShift Container Platform to a version that includes the fixed cri-o package containing the CVE-2022-27652 patch (e.g., OCP 4.9.41+, 4.10.12+, or later patched releases).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cri OApplication
Affected:all versions
Openshift Container PlatformApplication
Affected:= 3.11= 4.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenShift Container Platform version
    Run 'oc get clusterversion' or check /etc/redhat-release on a control plane node to determine the installed OCP version
    Affected if The version is 3.11 or 4.12 (exact match)
  2. Confirm cri-o runtime is in use
    Run 'crictl info' or check 'crio --version' on any node to verify cri-o is the container runtime
    Affected if cri-o is the active container runtime (vs containerd or docker)
  3. Check for vulnerable capability-equipped binaries
    Review any custom or third-party binaries on nodes that have file capabilities set (run 'getcap -r /' and look for programs with cap_setfcap, cap_setpcap, or similar capabilities in their permitted set)
    Affected if Programs with inheritable file capabilities exist and are accessible to potential attackers

A user is affected if they are running OpenShift Container Platform version 3.11 or 4.12 with cri-o as the container runtime and have programs with inheritable file capabilities on their nodes that could be exploited for privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenShift Container Platform to a version that includes the fixed cri-o package containing the CVE-2022-27652 patch (e.g., OCP 4.9.41+, 4.10.12+, or later patched releases).

Recommended fix Moderate confidence

OpenShift Container Platform: 4.9.41+, 4.10.12+, 4.11.13+, or 4.12+ (any z-stream release at or above these versions)

  1. For OpenShift Container Platform 4.9.x: Upgrade to version 4.9.41 or later which includes the fixed cri-o package via RHBA-2022:5433
  2. For OpenShift Container Platform 4.10.x: Upgrade to version 4.10.12 or later which includes the fixed cri-o package via RHSA-2022:1600
  3. For OpenShift Container Platform 4.11.x: Upgrade to version 4.11.13 or later to obtain the fixed cri-o
  4. For OpenShift Container Platform 4.12: Upgrade to the latest available 4.12.z release to obtain the fixed cri-o
  5. For standalone cri-o: Upgrade to the cri-o version that includes the fix for CVE-2022-27652 (refer to upstream cri-o release notes for version containing the fix)
  6. After upgrade, verify the cri-o version matches the expected patched version using: rpm -q cri-o or oc get nodes -o wide to confirm runtime
Caveat Standard OpenShift upgrade precautions apply including backup, maintenance window planning, and testing in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cri O Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3466 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data