Heap corruption via Profiles use-after-free
Published Nov 1, 2023 · Updated Apr 29, 2025
Use after free in the Profiles component of Google Chrome before 119.0.6045.105 allows remote attackers to corrupt heap memory. Google has not published the freed object, stale reference, or code path responsible for the invalid memory access. Exploitation requires a user to perform specific interface gestures, after which the attacker corrupts memory in the browser process.
Summary
What happened
Use after free in the Profiles component of Google Chrome before 119.0.6045.105 allows remote attackers to corrupt heap memory. Google has not published the freed object, stale reference, or code path responsible for the invalid memory access. Exploitation requires a user to perform specific interface gestures, after which the attacker corrupts memory in the browser process.
The record
- CVE
- CVE-2023-5854
- Published
- Nov 1, 2023
- Updated
- Apr 29, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2023CVE publishedPublication date reported by the CVE source.
- Apr 29, 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.105 <119.0.6045.105
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