Heap corruption via libavif use-after-free
Published Dec 14, 2023 · Updated Feb 13, 2025
Use-after-free in libavif in Google Chrome before 120.0.6099.109 allows remote attackers to corrupt heap memory via a crafted image. Google identifies libavif as the affected component but has not disclosed the object-lifetime error or call path that leaves freed memory reachable. User interaction is required to render the image, and the documented outcome is heap corruption rather than guaranteed process takeover.
Summary
What happened
Use-after-free in libavif in Google Chrome before 120.0.6099.109 allows remote attackers to corrupt heap memory via a crafted image. Google identifies libavif as the affected component but has not disclosed the object-lifetime error or call path that leaves freed memory reachable. User interaction is required to render the image, and the documented outcome is heap corruption rather than guaranteed process takeover.
The record
- CVE
- CVE-2023-6704
- Published
- Dec 14, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 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=120.0.6099.109 <120.0.6099.109
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