Availability loss via uncaught callback panic
Published Dec 26, 2021 · Updated Aug 5, 2024
Uncaught exceptions in libpulse-binding before 2.6.0 allow attackers to cause availability loss through panicking callbacks. Callback proxy functions invoke Rust callbacks without catch_unwind, so a panic can unwind through PulseAudio foreign stack frames. Reachability requires a consuming application to execute a callback that panics; the resulting undefined behavior has no published confidentiality or integrity impact.
Summary
What happened
Uncaught exceptions in libpulse-binding before 2.6.0 allow attackers to cause availability loss through panicking callbacks. Callback proxy functions invoke Rust callbacks without catch_unwind, so a panic can unwind through PulseAudio foreign stack frames. Reachability requires a consuming application to execute a callback that panics; the resulting undefined behavior has no published confidentiality or integrity impact.
The record
- CVE
- CVE-2019-25055
- Published
- Dec 26, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
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