Disputed host-file writes via procfs mount semantics
Published May 27, 2021 · Updated Aug 7, 2024
Reported improper access control in the Linux kernel allows local users to write host files from a chroot through a read-only procfs mount. The report mistakes the shared read-write procfs superblock for the separate per-vfsmount access mode that rejects writes with EROFS. The claim requires local access and mount capability inside a chroot, but Red Hat closed the case as not a bug because the claimed host-file write bypass was not established.
Summary
What happened
Reported improper access control in the Linux kernel allows local users to write host files from a chroot through a read-only procfs mount. The report mistakes the shared read-write procfs superblock for the separate per-vfsmount access mode that rejects writes with EROFS. The claim requires local access and mount capability inside a chroot, but Red Hat closed the case as not a bug because the claimed host-file write bypass was not established.
The record
- CVE
- CVE-2008-2544
- Published
- May 27, 2021
- Updated
- Aug 7, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 7, 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.
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
- Procfs chroot write reproduction procedureproof of concept · unverified
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