Heap corruption via crafted audio file
Published May 12, 2023 · Updated Oct 3, 2024
An out-of-bounds write in Google Chrome's ChromeOS Audio Server before 113.0.5672.114 allows remote attackers to corrupt heap memory. The public record identifies a crafted audio file as the trigger but does not disclose the affected function, buffer, or unchecked write. A user must process attacker-controlled audio; the documented consequence is heap corruption, with the exact post-corruption behavior undisclosed.
Summary
What happened
An out-of-bounds write in Google Chrome's ChromeOS Audio Server before 113.0.5672.114 allows remote attackers to corrupt heap memory. The public record identifies a crafted audio file as the trigger but does not disclose the affected function, buffer, or unchecked write. A user must process attacker-controlled audio; the documented consequence is heap corruption, with the exact post-corruption behavior undisclosed.
The record
- CVE
- CVE-2023-2457
- Published
- May 12, 2023
- Updated
- Oct 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2023CVE publishedPublication date reported by the CVE source.
- Oct 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <113.0.5672.114
- Affected versionversion=113.0.5672.114 <113.0.5672.114
What conditions does exploitation require?
What is affected?
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