Browser crash via concurrent audio-input ownership
Published May 14, 2024 · Updated Aug 1, 2024
Use-after-free in Firefox WebRTC before 126 allows attackers to crash the browser when multiple threads claim a newly connected audio input. Competing WebRTC threads can both claim the same new input, so teardown frees an audio object while another consumer still uses it. Reproduction requires multiple active WebRTC consumers and an audio-device connection change; Mozilla's public case used two Meet tabs and AirPods on macOS.
Summary
What happened
Use-after-free in Firefox WebRTC before 126 allows attackers to crash the browser when multiple threads claim a newly connected audio input. Competing WebRTC threads can both claim the same new input, so teardown frees an audio object while another consumer still uses it. Reproduction requires multiple active WebRTC consumers and an audio-device connection change; Mozilla's public case used two Meet tabs and AirPods on macOS.
The record
- CVE
- CVE-2024-4764
- Published
- May 14, 2024
- Updated
- Aug 1, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=126* <126
- Affected versionversion=unspecified <126
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