Root privilege escalation via stale process port
Published Nov 7, 2021 · Updated Aug 4, 2024
A setuid exec race in GNU Hurd before 0.9 20210404-9 allows local users to gain full root access through an old process port. The exec path separately reauthenticates the process, assigns its replacement task, and invalidates the old process port, exposing a privileged transition window. A local account that can run a setuid executable and retain the old process port can control the newly privileged process.
Summary
What happened
A setuid exec race in GNU Hurd before 0.9 20210404-9 allows local users to gain full root access through an old process port. The exec path separately reauthenticates the process, assigns its replacement task, and invalidates the old process port, exposing a privileged transition window. A local account that can run a setuid executable and retain the old process port can control the newly privileged process.
The record
- CVE
- CVE-2021-43411
- Published
- Nov 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, 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 Hurd setuid exec race demonstrationproof 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