Skip to content
Fencer Intel
high 7.1

CVE-2022-2995 json

CRI-O incorrect handling of supplementary groups may lead to sensitive information disclosure

published 4y ago modified 4mo ago also GHSA-phjr-8j92-w5v7 , GO-2022-1014 , EUVD-2022-6897

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

Summary

Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.

Patch / fix

  • go github.com/cri-o/cri-o 1.25.0
  • tox openshift ironic 4.12 3.23.0-2.el9.1
  • crit openshift 4.12 3.15-4.rhaos4.11.el8
  • criu openshift 4.12 3.15-4.rhaos4.11.el8
  • crun openshift 4.12 1.4.2-1.rhaos4.11.el8
  • crun openshift 4.12 1.4.2-2.rhaos4.12.el9
  • grpc openshift 4.12 1.18.0-4.el8ost
  • runc openshift 4.12 3:1.1.2-2.rhaos4.12.el8
  • tini openshift 4.12 0.16.1-1.el8ar

red hat advisories RHSA-2022:7398RHSA-2023:3541RHSA-2023:3216

  • cri-o CBL-Mariner 2.0 1.21.7-2

azure linux advisories AZL-39882

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2022-2995 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-2995 updated cvss 3.6

cri-o: incorrect handling of the supplementary groups

  • Red Hat OpenShift Container Platform 3.11 cri-o
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Container Platform 4.10 cri-o 1.23.5-11.rhaos4.10.gitfc32aac.el7, cri-o 1.23.5-11.rhaos4.10.gitfc32aac.el8
    fixed: vendor fix RHSA-2023:3216
  • Red Hat OpenShift Container Platform 4.11 cri-o 1.24.5-5.rhaos4.11.git8bf967b.el8
    fixed: vendor fix RHSA-2023:3541
  • Red Hat OpenShift Container Platform 4.12 cri-o 1.25.1-5.rhaos4.12.git6005903.el8, cri-o 1.25.1-5.rhaos4.12.git6005903.el9
    fixed: vendor fix RHSA-2022:7398
  • Red Hat Ironic content for Red Hat OpenShift Container Platform 4.11 python-flask 1.1.2-6.el8, python3-flask 1.1.2-6.el8, openstack-ironic 20.2.1-0.20230605115028.483a7f9.el8, openstack-ironic-api 20.2.1-0.20230605115028.483a7f9.el8, python3-ironic-tests 20.2.1-0.20230605115028.483a7f9.el8, openstack-ironic-common 20.2.1-0.20230605115028.483a7f9.el8, +2 more Red Hat Ironic content for Red Hat OpenShift Container Platform 4.12 tox 3.23.0-2.el9.1, crudini 0.9.3-4.el9, pysnmp 4.4.12-6.el9, future 0.18.2-9.el9.1, subunit 1.4.0-6.el9.1, pyflakes 2.2.0-3.el9.1, +451 more Red Hat OpenShift Container Platform 4.10 jenkins 2.387.3.1684251986-1.el8, openshift-kuryr 4.10.0-202305161315.p0.g8e4df8b.assembly.stream.el8, openshift-kuryr-cni 4.10.0-202305161315.p0.g8e4df8b.assembly.stream.el8, openshift-kuryr-common 4.10.0-202305161315.p0.g8e4df8b.assembly.stream.el8, python3-kuryr-kubernetes 4.10.0-202305161315.p0.g8e4df8b.assembly.stream.el8, openshift-kuryr-controller 4.10.0-202305161315.p0.g8e4df8b.assembly.stream.el8 Red Hat OpenShift Container Platform 4.11 openshift 4.11.0-202305261554.p0.g38b1413.assembly.stream.el8, openshift-hyperkube 4.11.0-202305261554.p0.g38b1413.assembly.stream.el8 Red Hat OpenShift Container Platform 4.12 nmstate 1.3.3-1.el8, ostree 2022.2-5.el8, tini 0.16.1-1.el8ar, buildah 1.23.4-2.el8, grpc 1.18.0-4.el8ost, haproxy 2.2.24-1.el8, +236 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • benthamsgaze.org https://www.benthamsgaze.org/2022/08/22/vulnerability-in-linux-containers-investigation-and-mitigation/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/cri-o/cri-o
<1.25.0
1.25.0

Affected products

  • n/a cri-o

Classification

Weakness
  • CWE-284 Improper Access Control
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.