Privilege escalation via emergency-file symlink race
Published Jun 12, 2024 · Updated Nov 21, 2025
Link-following in GNU nano before 8.0 allows local users to gain privileges by replacing a crash-recovery file with a symlink. Emergency-save handling creates a .save file, then applies chmod and chown by pathname, allowing a writable-directory user to swap in a symlink before those calls. Exploitation requires a privileged nano process editing a user-controlled file and a way for the local user to terminate that process during the race.
Summary
What happened
Link-following in GNU nano before 8.0 allows local users to gain privileges by replacing a crash-recovery file with a symlink. Emergency-save handling creates a .save file, then applies chmod and chown by pathname, allowing a writable-directory user to swap in a symlink before those calls. Exploitation requires a privileged nano process editing a user-controlled file and a way for the local user to terminate that process during the race.
The record
- CVE
- CVE-2024-5742
- Published
- Jun 12, 2024
- Updated
- Nov 21, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-59, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 2025Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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