CVE-2022-4122

A vulnerability was found in buildah. Incorrect following of symlinks while reading .containerignore and .dockerignore results in information disclosure.

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-4122 is rated Low Risk (35.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.19%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-4122

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 2025-12-22 0.13% 0.19% +0.06%
2 2025-11-21 0.22% 0.13% -0.10%
3 2025-11-18 — 0.22% —

Full EPSS history (8 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N)
No account or special rights needed—anonymous or random user is enough.
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.
 3.9 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N)
No account or special rights needed—anonymous or random user is enough.
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.
 3.9 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-4122

GitHub Security Advisory for CVE-2022-4122

GHSA-4crw-w8pw-2hmf · Severity: medium · Ecosystem: go — Buildah (as part of Podman) vulnerable to Link Following

OS Trackers for CVE-2022-4122

vendor priority summary link
alpine — CVE-2022-4122: 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-4122
debian unimportant CVE-2022-4122 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-4122
redhat medium — https://access.redhat.com/security/cve/CVE-2022-4122
suse medium CVE-2022-4122 severity moderate: SUSE including 6 source package names (buildah, podman-5.2.2-1.el9, podman-docker-5.2.2-1.el9, podman-plugins-5.2.2-1.el9, podman-remote-5.2.2-1.el9, podman-tests-5.2.2-1.el9), 38 product×package rows across 34 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 6, … (34 product lines)): Known Not Affected 33, Fixed 5. https://www.suse.com/security/cve/CVE-2022-4122/
ubuntu medium CVE-2022-4122 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-4122

Affected software / configurations for CVE-2022-4122

Vendor Product Version Raw CPE
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-4122

URL Tags
https://bugzilla.redhat.com/show_bug.cgi?id=2144983 Issue Tracking Third Party Advisory
https://github.com/containers/podman/pull/16315 Patch Third Party Advisory
cvelogic Threat Intelligence