LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2989: An incorrect handling of the supplementary groups in the Podman container engine might lead to the sensitiv...

An incorrect handling of the supplementary groups in the Podman container engine might lead to the 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

Podman may mishandle supplementary Linux groups inside containers. If an attacker already has access to an affected container and can run code there, they may read sensitive information or modify data protected by group-based permissions.

Executive priority

Treat as high priority for environments using Podman with group-based access controls inside containers. Urgency is lower where containers are single-purpose, trusted, and do not expose sensitive group-protected resources.

Technical view

CVE-2022-2989 is a Podman supplementary-group handling flaw mapped to CWE-842. The CVSS 3.1 vector is local, low complexity, low privileges, no user interaction, with high confidentiality and integrity impact and no availability impact.

Likely exposure

Exposure is most likely where Podman containers rely on supplementary groups to enforce file or data access boundaries, especially multi-user or semi-trusted container workloads. The source bundle lists no fixed version known.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires direct access to the affected container and the ability to execute binary code inside it.

Researcher notes

The public record is concise and does not name a fixed version. Analysis should focus on supplementary group propagation, container access assumptions, and whether group-based permissions protect sensitive files or writable data paths.

Mitigation direction

  • Review Red Hat Bugzilla and Podman vendor guidance for current fixed builds or mitigations.
  • Avoid relying on supplementary groups as the sole access boundary inside affected containers.
  • Reduce direct shell or code execution access in containers using group-based permissions.
  • Audit sensitive files and mounted volumes protected by supplementary group membership.
  • Prioritize runtime updates once vendor-confirmed fixed packages are identified.

Validation and detection

  • Inventory Podman deployments and record versions in production and development environments.
  • Identify containers where supplementary groups are used for access permissions.
  • Check whether untrusted users or workloads can execute code inside those containers.
  • Review mounted volumes and sensitive paths protected by group permissions.
  • Track vendor advisories for a confirmed fixed version or documented workaround.
Prepared
Confidence
medium
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 · low confidence lookup

CWE-842: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2989 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-2989Attack 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/apodmanno fixed version knownListed
Weakness

CWE details

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

CWE-842 · source CWE mapping

Placement of User into Incorrect Group

Placement of User into Incorrect Group represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.