Heap corruption via libavif use after free
Published Nov 29, 2023 · Updated Feb 13, 2025
Use after free in Google Chrome's libavif before 119.0.6045.199 allows remote attackers to trigger heap corruption with a crafted AVIF file. The libavif decoding path accesses an allocation after release; Google has not disclosed the affected function or lifetime transition. Chrome must process attacker-controlled AVIF content, and successful exploitation can compromise the browser process within Chrome's security boundary.
Summary
What happened
Use after free in Google Chrome's libavif before 119.0.6045.199 allows remote attackers to trigger heap corruption with a crafted AVIF file. The libavif decoding path accesses an allocation after release; Google has not disclosed the affected function or lifetime transition. Chrome must process attacker-controlled AVIF content, and successful exploitation can compromise the browser process within Chrome's security boundary.
The record
- CVE
- CVE-2023-6351
- Published
- Nov 29, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=119.0.6045.199 <119.0.6045.199
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.
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