Local root escalation via forged port notifications
Published Nov 7, 2021 · Updated Aug 4, 2024
Use-after-free in libports in GNU Hurd before 0.9 20210404-9 allows local users to gain full root access via forged notifications. The notification handlers trust client-supplied no-senders and dead-name messages as kernel notifications, decrementing object references or deallocating chosen port names. Any local user holding a send right to a libports-managed port can trigger stale port reuse and obtain full root privileges.
Summary
What happened
Use-after-free in libports in GNU Hurd before 0.9 20210404-9 allows local users to gain full root access via forged notifications. The notification handlers trust client-supplied no-senders and dead-name messages as kernel notifications, decrementing object references or deallocating chosen port names. Any local user holding a send right to a libports-managed port can trigger stale port reuse and obtain full root privileges.
The record
- CVE
- CVE-2021-43412
- Published
- Nov 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, 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.
Public exploit references
- GNU Hurd fake-notification root exploitfunctional · 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