LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2995: Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive inform...

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-2995 is a CRI-O container engine flaw where supplementary Linux groups may be handled incorrectly. In affected containers, a user who can run code may gain unintended group-based access to sensitive files or modify data that group permissions were meant to protect.

Executive priority

Treat as high priority for CRI-O-based clusters, especially multi-tenant or sensitive workloads. It is not described as remote internet exploitation, but it can undermine container isolation assumptions where group permissions protect data.

Technical view

The issue affects CRI-O 1.25.0 and is classified as CWE-284. The CVSS 3.1 score is 7.1 with local attack vector, low complexity, low privileges, no user interaction, and high confidentiality and integrity impact. The condition depends on containers using supplementary groups for access control.

Likely exposure

Exposure is most likely in Kubernetes or container environments running CRI-O 1.25.0 where workloads rely on supplementary groups to protect mounted files, shared volumes, or other sensitive resources.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires direct access to an affected container and the ability to execute code inside it, plus relevant group-based permissions.

Researcher notes

Evidence is strongest for CRI-O 1.25.0 and the supplementary-groups access-control condition. The bundle does not provide a fixed version, exploit-in-the-wild evidence, or full downstream distro impact, so validation should focus on runtime version and workload permission design.

Mitigation direction

  • Inventory CRI-O deployments and identify any running version 1.25.0.
  • Review CRI-O PR 6159 and downstream vendor guidance for corrected builds.
  • Prioritize upgrades where workloads use supplementary groups for sensitive access controls.
  • Review mounted data, group ownership, and write permissions in affected containers.
  • Limit who can execute code or obtain shells inside sensitive containers.

Validation and detection

  • Confirm whether any cluster nodes run CRI-O 1.25.0.
  • Identify workloads that set or rely on supplementary groups.
  • Check whether those workloads mount sensitive files or shared writable volumes.
  • Verify deployed CRI-O packages include the upstream or vendor correction.
  • Document any compensating controls for containers that cannot be updated immediately.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-2995 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N1.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2022-2995Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/acri-ocri-o 1.25.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.