An incorrect handling of the supplementary groups in the Buildah 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.
CVE-2022-2990
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.3% (26th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 32EG Risk 32/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity71% × 45%The EG Score, 7.1 of 10.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 26th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 13, 2022
Last Modified
November 21, 2024
References (2)
- secalert@redhat · CVE Programhttps://bugzilla.redhat.com/show_bug.cgi?id=2121453Exploit · Issue Tracking · Patch · Third Party Advisory
- secalert@redhat · CVE Programhttps://www.benthamsgaze.org/2022/08/22/vulnerability-in-linux-containers-investigation-and-mitigation/Exploit · Third Party Advisory
Vendor Advisories for CVE-2022-2990(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2023:1325Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.13.0 security update
- RHSA-2022:8008Red Hat Product SecurityMedium
Red Hat Security Advisory: buildah security and bug fix update
- RHSA-2022:7457Red Hat Product SecurityMedium
Red Hat Security Advisory: container-tools:rhel8 security, bug fix, and enhancement update
- CVE-2022-2990Microsoft Security Response Center (MSRC)High
An incorrect handling of the supplementary groups in the Buildah 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.
Patch Availability(5)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | buildah-1:1.29.1-1.rhaos4.13.el9 | 2023-05-18 | redhat |
| redhat | podman-2:4.2.0-7.el9_1 | 2022-11-15 | redhat |
| redhat | buildah-1:1.27.0-2.el9 | 2022-11-15 | redhat |
| redhat | container-tools:rhel8-8070020220929222448.39077419 | 2022-11-08 | redhat |
| redhat | container-tools:rhel8-8070020221026183352.489fc8e9 | 2022-11-08 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-containers-buildah | 1.19.6+dfsg1-1 ... 1.43.2+ds1-1 (77 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-containers-buildah | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-containers-buildah | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-containers-buildah | — |
| — |
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/containers/buildah | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 9× in last 7d / 30× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 91 of 184 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-12 18:55 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-11 23:20 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-30 15:54 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-28 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-26 15:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-24 11:37 UTCOSV refresh
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-22 14:44 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.3% · 28th percentile
Show 66 moreShow fewer
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-18 19:24 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-15 03:06 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-11 14:49 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-05 04:18 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-23 00:16 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-18 14:58 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-13 21:57 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-11 13:38 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-03 10:57 UTCOSV refresh
- 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-25 14:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-23 02:10 UTCEG score recompute
- 2026-07-22 22:57 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-21 15:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-20 17:05 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-19 14:29 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-19 02:27 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-18 10:02 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-16 20:20 UTCOSV refresh
- 2026-07-16 17:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-15 16:56 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-07-15 01:58 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownGo:github.com/containers/buildah · Debian:11:golang-github-containers-buildah
Same vendor
10 shownredhat:RHSA-2022:7457 · redhat:RHSA-2022:7822 · redhat:RHSA-2023:1325
Frequently asked(5)
What is CVE-2022-2990?
When was the CVE record for CVE-2022-2990 published?
Is CVE-2022-2990 actively exploited?
What is the CVSS score of CVE-2022-2990?
How do I remediate CVE-2022-2990?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-2990
Is Your Infrastructure Affected by CVE-2022-2990?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.