Root privilege escalation via shared pager port
Published Nov 7, 2021 · Updated Aug 4, 2024
GNU Hurd before 0.9 20210404-9 allows local users to gain root by modifying readable files through memory mappings. A single pager port is reused for every process mapping the same file, so a reader's writable mapping can change the shared backing file despite lacking write permission. Local access and read permission on a privileged file are sufficient to alter protected data and escalate to full root access.
Summary
What happened
GNU Hurd before 0.9 20210404-9 allows local users to gain root by modifying readable files through memory mappings. A single pager port is reused for every process mapping the same file, so a reader's writable mapping can change the shared backing file despite lacking write permission. Local access and read permission on a privileged file are sufficient to alter protected data and escalate to full root access.
The record
- CVE
- CVE-2021-43413
- Published
- Nov 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- GNU bug-hurd pager-port exploit postproof 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