Memory access via undisclosed Blink bounds error
Published Feb 21, 2024 · Updated Feb 13, 2025
Out-of-bounds memory access in Blink in Google Chrome before 122.0.6261.57 allows remote attackers to access memory via crafted HTML. Google has not publicly disclosed the affected Blink code locus or the incorrect bounds operation, and the linked issue requires sign-in. The gate is rendering attacker-controlled HTML; public records do not establish whether the access is a read, write, or both.
Summary
What happened
Out-of-bounds memory access in Blink in Google Chrome before 122.0.6261.57 allows remote attackers to access memory via crafted HTML. Google has not publicly disclosed the affected Blink code locus or the incorrect bounds operation, and the linked issue requires sign-in. The gate is rendering attacker-controlled HTML; public records do not establish whether the access is a read, write, or both.
The record
- CVE
- CVE-2024-1669
- Published
- Feb 21, 2024
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, CWE-125, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 21, 2024CVE 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=122.0.6261.57 <122.0.6261.57
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.
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