cve.bz

CVE-2022-4123 Relative Path Traversal

3.3 lowEPSS 0.3%

Low (3.3). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-23 Relative Path Traversal
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-4123 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-4123?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-4123?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-4123 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
podman_project:podman4.1.0
podman_project:podman4.1.0:rc1
podman_project:podman4.1.0:rc2
podman_project:podman4.1.1
podman_project:podman4.2.0
podman_project:podman4.2.0:rc1
podman_project:podman4.2.0:rc2
podman_project:podman4.2.0:rc3
podman_project:podman4.2.1
podman_project:podman4.3.0
fedoraproject:fedora35
fedoraproject:fedora36
fedoraproject:fedora37

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rprg-4v7q-87v7Gogithub.com/containers/podman/v4>=4.1.0-rc1 <=4.4.1no fix published
GO-2022-1159Gogithub.com/containers/podman/v4>=4.1.0-rc1no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14golang-github-containers-buildahno fix listedDEBIAN-CVE-2022-4123
Ubuntu22.04:LTS, 25.10, 26.10 and 2 moregolang-github-containers-buildahno fix listedUBUNTU-CVE-2022-4123
Azure Linux2podmanno fix listedAZL-11587
Azure Linux3podman5.6.1-2AZL-36977

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Low.

Red Hat's statement

These bugs come about when "podman --remote build -t test1 -f /tmp/Dockerfile> emptydir" is run, thus affecting buildah, but the bug itself needs to be fixed in podman, and ported to Buildah.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 7buildahOut of support scope
Red Hat Enterprise Linux 7podmanOut of support scope
Red Hat Enterprise Linux 8container-tools:3.0/podmanNot affected
Red Hat Enterprise Linux 8container-tools:4.0/podmanFix deferred
Red Hat Enterprise Linux 8container-tools:rhel8/podmanFix deferred
Red Hat Enterprise Linux 9podmanFix deferred
Red Hat OpenShift Container Platform 3.11podmanUnder investigation
Red Hat OpenShift Container Platform 4buildahAffected
Red Hat OpenShift Container Platform 4podmanUnder investigation

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-4123.

Attack patterns (CAPEC)

  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-139 Relative Path Traversal Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON