Process crash via panic-reporting double unwind
Published Jul 18, 2023 · Updated Aug 3, 2024
Denial of service in OSTree before 2022.7 and its Rust crate before 0.17.1 allows attackers to abort a consuming process. The print_panic function uses eprintln! while handling a caught checkout-filter callback panic; a failed stderr write causes a second panic to unwind across the C ABI boundary. Exploitation requires both a callback panic and an stderr write failure, and the demonstrated consequence is a process crash rather than data disclosure or modification.
Summary
What happened
Denial of service in OSTree before 2022.7 and its Rust crate before 0.17.1 allows attackers to abort a consuming process. The print_panic function uses eprintln! while handling a caught checkout-filter callback panic; a failed stderr write causes a second panic to unwind across the C ABI boundary. Exploitation requires both a callback panic and an stderr write failure, and the demonstrated consequence is a process crash rather than data disclosure or modification.
The record
- CVE
- CVE-2022-47085
- Published
- Jul 18, 2023
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 18, 2023CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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