Heap corruption via QR generator use-after-free
Published Jul 22, 2022 · Updated Aug 2, 2024
Use after free in Google Chrome's QR Code Generator before 100.0.4896.60 allows remote attackers to corrupt heap memory. Google identifies the locus and invalid memory-lifetime operation, but the restricted issue omits the affected object and code path. The gate is a specific user interaction with remote content, and the bounded reported consequence is browser heap corruption.
Summary
What happened
Use after free in Google Chrome's QR Code Generator before 100.0.4896.60 allows remote attackers to corrupt heap memory. Google identifies the locus and invalid memory-lifetime operation, but the restricted issue omits the affected object and code path. The gate is a specific user interaction with remote content, and the bounded reported consequence is browser heap corruption.
The record
- CVE
- CVE-2022-1127
- Published
- Jul 22, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=unspecified <100.0.4896.60
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