CVE-2022-2989

Exp

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.

Published: 2022-09-13 Last update: 2025-06-05 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-2989 is rated Exploit Available (50/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-2989

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-2989

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-04 0.05% 0.05% -0.00%
2 2026-02-20 0.04% 0.05% +0.01%
3 2025-11-21 — 0.04% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-2989

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 5.2 [email protected]
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-2989

GitHub Security Advisory for CVE-2022-2989

GHSA-4wjj-jwc9-2x96 · Severity: high · Ecosystem: go — Podman's incorrect handling of the supplementary groups may lead to data disclosure, modification

OS Trackers for CVE-2022-2989

vendor priority summary link
alpine — CVE-2022-2989: 1 source package rows (podman); 146 state rows across 8 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, 3.23-community, edge-community); fixed 134, open 12. https://security.alpinelinux.org/vuln/CVE-2022-2989
debian not yet assigned CVE-2022-2989 not yet assigned priority: Debian including 1 source packages (libpod), 2 status rows across 2 suites (bookworm, bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2022-2989
gentoo high CVE-2022-2989: 1 GLSA(s) (202407-12), 1 atom(s) (app-containers/podman); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-2989
redhat low — https://access.redhat.com/security/cve/CVE-2022-2989
suse medium CVE-2022-2989 severity moderate: SUSE including 80 source package names (aardvark-dns-1.1.0-5.module+el8.7.0+17064+3b31f55c, buildah-1.27.0-2.el9, …), 137 product×package rows across 44 product lines (Container rancher/elemental-teal-rt/5.4, Container rancher/elemental-teal/5.4, … (44 product lines)): Fixed 112, Will Not Fix 25. https://www.suse.com/security/cve/CVE-2022-2989/
ubuntu medium CVE-2022-2989 medium priority: Ubuntu including 1 source packages (libpod), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 6, ignored 4, needs-triage 2, released 1. https://ubuntu.com/security/CVE-2022-2989

Affected software / configurations for CVE-2022-2989

Vendor Product Version Raw CPE
podman_project podman — cpe:2.3:a:podman_project:podman:*:*:*:*:*:*:*:*
redhat openshift_container_platform 3.11 cpe:2.3:a:redhat:openshift_container_platform:3.11:*:*:*:*:*:*:*
redhat openshift_container_platform 4.0 cpe:2.3:a:redhat:openshift_container_platform:4.0:*:*:*:*:*:*:*
redhat enterprise_linux 7.0 cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*
redhat enterprise_linux 8.0 cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*
redhat enterprise_linux 9.0 cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*

References for CVE-2022-2989

cvelogic Threat Intelligence