Host file overwrite via symlink-exchange race
Published Sep 23, 2024 · Updated Sep 23, 2024
Race condition in Pouch Engine 1.3.1 allows attackers controlling a container to write arbitrary files on the host filesystem. The ExtractToDir path in daemon/mgr/container_copy.go checks the destination with os.Lstat, then chrootarchive.Untar resolves it after a container can replace it with a symlink. Exploitation requires control of the target container and an administrator-initiated pouch cp operation; a won race redirects archive extraction outside the container and can overwrite host files.
Summary
What happened
Race condition in Pouch Engine 1.3.1 allows attackers controlling a container to write arbitrary files on the host filesystem. The ExtractToDir path in daemon/mgr/container_copy.go checks the destination with os.Lstat, then chrootarchive.Untar resolves it after a container can replace it with a symlink. Exploitation requires control of the target container and an administrator-initiated pouch cp operation; a won race redirects archive extraction outside the container and can overwrite host files.
The record
- CVE
- CVE-2024-41228
- Published
- Sep 23, 2024
- Updated
- Sep 23, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1611
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 23, 2024CVE publishedPublication date reported by the CVE source.
- Sep 23, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
- Pouch container exists TOCTTOU proof of conceptproof of concept · demonstrated
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