Application crash via null dereference in find
Published Jan 14, 2022 · Updated Aug 4, 2024
NULL pointer dereference in ROPium 3.1 allows local users to crash the application by invoking find after a failed file load. After load -a X64 rejects a nonexistent file, find still reaches an instruction that reads through the null RSI register. Access to an interactive ROPium session is required, and the demonstrated consequence is a segmentation fault that terminates only that process.
Summary
What happened
NULL pointer dereference in ROPium 3.1 allows local users to crash the application by invoking find after a failed file load. After load -a X64 rejects a nonexistent file, find still reaches an instruction that reads through the null RSI register. Access to an interactive ROPium session is required, and the demonstrated consequence is a segmentation fault that terminates only that process.
The record
- CVE
- CVE-2021-45761
- Published
- Jan 14, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 14, 2022CVE 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
- ROPium find() crash 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