CVE-2022-4123

A flaw was found in Buildah. The local path and the lowest subdirectory may be disclosed due to incorrect absolute path traversal, resulting in an impact to confidentiality.

Published: 2022-12-08 Last update: 2025-04-22 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-4123 is rated Low Risk (19.1/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.05%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

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

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

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-05-17 0.04% 0.05% +0.01%
2 2023-03-07 0.89% 0.04% -0.84%
3 2022-12-09 — 0.89% —

Full EPSS history (3 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 1.4 [email protected]
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-4123

GitHub Security Advisory for CVE-2022-4123

GHSA-rprg-4v7q-87v7 · Severity: low · Ecosystem: go — Buildah (as part of Podman) vulnerable to Path Traversal

OS Trackers for CVE-2022-4123

vendor priority summary link
alpine — CVE-2022-4123: 1 source package rows (podman); 3 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2022-4123
debian unimportant CVE-2022-4123 unimportant priority: Debian including 1 source packages (golang-github-containers-buildah), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2022-4123
redhat low — https://access.redhat.com/security/cve/CVE-2022-4123
suse low CVE-2022-4123 severity low: SUSE including 1 source package names (buildah), 16 product×package rows across 16 product lines (SUSE Enterprise Storage 7.1, SUSE Linux Enterprise High Performance Computing 15 SP3-ESPOS, … (16 product lines)): Known Not Affected 16. https://www.suse.com/security/cve/CVE-2022-4123/
ubuntu medium CVE-2022-4123 medium priority: Ubuntu including 1 source packages (golang-github-containers-buildah), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, needs-triage 4, DNE 2. https://ubuntu.com/security/CVE-2022-4123

Affected software / configurations for CVE-2022-4123

Vendor Product Version Raw CPE
podman_project podman 4.1.0 cpe:2.3:a:podman_project:podman:4.1.0:-:*:*:*:*:*:*
podman_project podman 4.1.0 cpe:2.3:a:podman_project:podman:4.1.0:rc1:*:*:*:*:*:*
podman_project podman 4.1.0 cpe:2.3:a:podman_project:podman:4.1.0:rc2:*:*:*:*:*:*
podman_project podman 4.1.1 cpe:2.3:a:podman_project:podman:4.1.1:*:*:*:*:*:*:*
podman_project podman 4.2.0 cpe:2.3:a:podman_project:podman:4.2.0:-:*:*:*:*:*:*
podman_project podman 4.2.0 cpe:2.3:a:podman_project:podman:4.2.0:rc1:*:*:*:*:*:*
podman_project podman 4.2.0 cpe:2.3:a:podman_project:podman:4.2.0:rc2:*:*:*:*:*:*
podman_project podman 4.2.0 cpe:2.3:a:podman_project:podman:4.2.0:rc3:*:*:*:*:*:*
podman_project podman 4.2.1 cpe:2.3:a:podman_project:podman:4.2.1:*:*:*:*:*:*:*
podman_project podman 4.3.0 cpe:2.3:a:podman_project:podman:4.3.0:-:*:*:*:*:*:*
fedoraproject fedora 35 cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
fedoraproject fedora 36 cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
fedoraproject fedora 37 cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*

References for CVE-2022-4123

URL Tags
https://bugzilla.redhat.com/show_bug.cgi?id=2144989 Issue Tracking Third Party Advisory
cvelogic Threat Intelligence