UI spoofing through crafted Autofill interactions
Published Nov 12, 2024 · Updated Nov 13, 2024
Inappropriate implementation in Google Chrome Autofill before 131.0.6778.69 allows remote attackers to spoof browser UI via crafted HTML. Google identifies Autofill as the locus but has not publicly disclosed which operation mishandles the crafted page or gesture sequence. Exploitation requires user interaction with specific UI gestures, and the documented consequence is alteration of displayed browser UI rather than data disclosure or service interruption.
Summary
What happened
Inappropriate implementation in Google Chrome Autofill before 131.0.6778.69 allows remote attackers to spoof browser UI via crafted HTML. Google identifies Autofill as the locus but has not publicly disclosed which operation mishandles the crafted page or gesture sequence. Exploitation requires user interaction with specific UI gestures, and the documented consequence is alteration of displayed browser UI rather than data disclosure or service interruption.
The record
- CVE
- CVE-2024-11111
- Published
- Nov 12, 2024
- Updated
- Nov 13, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-79, T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 13, 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=131.0.6778.69 <131.0.6778.69
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.
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