Root escalation via unconfirmed process reauthentication
Published Nov 7, 2021 · Updated Aug 4, 2024
Improper authentication in GNU Hurd before 0.9 20210404-9 allows local users to gain root access through the proc server. The proc server updates a process's UIDs on the original port after authentication instead of requiring confirmation on a newly authenticated port. A low-privileged local user must place a controlled port among a privileged process's file descriptors and induce reauthentication during execution.
Summary
What happened
Improper authentication in GNU Hurd before 0.9 20210404-9 allows local users to gain root access through the proc server. The proc server updates a process's UIDs on the original port after authentication instead of requiring confirmation on a newly authenticated port. A low-privileged local user must place a controlled port among a privileged process's file descriptors and induce reauthentication during execution.
The record
- CVE
- CVE-2021-43414
- Published
- Nov 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287, 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
- Process authentication man-in-the-middle 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