UI spoofing through undisclosed Autofill implementation
Published Sep 17, 2024 · Updated Mar 20, 2025
UI spoofing in Autofill in Google Chrome before 129.0.6668.58 allows remote attackers to misrepresent browser interface elements. Google has not published the faulty Autofill operation; the Chromium issue is access-restricted and the release notes identify only the component. Exploitation requires a crafted HTML page and user interaction, and the published impact is limited to changing what the user sees or trusts.
Summary
What happened
UI spoofing in Autofill in Google Chrome before 129.0.6668.58 allows remote attackers to misrepresent browser interface elements. Google has not published the faulty Autofill operation; the Chromium issue is access-restricted and the release notes identify only the component. Exploitation requires a crafted HTML page and user interaction, and the published impact is limited to changing what the user sees or trusts.
The record
- CVE
- CVE-2024-8908
- Published
- Sep 17, 2024
- Updated
- Mar 20, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-290, T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2024CVE publishedPublication date reported by the CVE source.
- Mar 20, 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=129.0.6668.58 <129.0.6668.58
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.
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