Host-file disclosure via symlinked ignore files
Published Dec 8, 2022 · Updated Apr 22, 2025
Information disclosure in Podman 4.3.0 allows remote attackers to read host files by supplying a symlinked container ignore file. During podman build, embedded Buildah opens .containerignore or .dockerignore through a symbolic link without rejecting link resolution, so referenced host-file contents are consumed. Exploitation requires control of a build context and exposes only files readable by the account running the build.
Summary
What happened
Information disclosure in Podman 4.3.0 allows remote attackers to read host files by supplying a symlinked container ignore file. During podman build, embedded Buildah opens .containerignore or .dockerignore through a symbolic link without rejecting link resolution, so referenced host-file contents are consumed. Exploitation requires control of a build context and exposes only files readable by the account running the build.
The record
- CVE
- CVE-2022-4122
- Published
- Dec 8, 2022
- Updated
- Apr 22, 2025
- Vendor
- Podman Container Tools
- Product
- Podman
- Classifications
- CWE-59, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 8, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Podman 4.3.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo