Skip to main content
Vulnerability Database/CVE-2024-11111

CVE-2024-11111: Google Chrome Autofill XSS Vulnerability

CVE-2024-11111 is a cross-site scripting vulnerability in Google Chrome Autofill that enables UI spoofing attacks through malicious HTML pages. This article covers the technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-11111 Overview

CVE-2024-11111 is a user interface (UI) spoofing vulnerability in the Autofill component of Google Chrome versions prior to 131.0.6778.69. A remote attacker can craft a malicious HTML page that misrepresents browser UI elements when a user performs specific interaction gestures. The flaw is tracked as an inappropriate implementation issue and is associated with [CWE-79]. Google rates the Chromium security severity as Medium.

Successful exploitation requires user interaction and does not grant code execution. The primary risk is deception of users into trusting attacker-controlled content presented through legitimate-looking Autofill UI.

Critical Impact

Attackers can spoof trusted browser UI through the Autofill component, enabling phishing-style deception that may lead to credential or payment data disclosure.

Affected Products

  • Google Chrome versions prior to 131.0.6778.69 (Desktop Stable channel)
  • Chromium-based browsers incorporating the vulnerable Autofill implementation
  • All supported desktop platforms (Windows, macOS, Linux) running pre-131 Chrome builds

Discovery Timeline

  • 2024-11-12 - CVE-2024-11111 published to NVD alongside the Chrome Stable channel update
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-11111

Vulnerability Analysis

The vulnerability resides in the Autofill subsystem of Chrome, which populates form fields with saved user data such as addresses, payment information, and contact details. An inappropriate implementation allows a crafted HTML page to manipulate how Autofill UI surfaces are rendered or triggered. When a user performs specific gestures on the attacker's page, the Autofill UI can be used to display misleading content.

Because the attack surface is the browser chrome rather than the renderer sandbox, the impact is limited to integrity of the displayed information. No confidentiality or availability loss is reported, and no sandbox escape is involved. The attack requires user interaction, which constrains large-scale automated exploitation.

Root Cause

The root cause is improper handling of UI state within the Autofill component when a page issues specific interaction sequences. The implementation does not sufficiently validate the context in which Autofill prompts are rendered, allowing a malicious page to influence their appearance or placement. This maps to [CWE-79] in NVD and reflects a broader class of UI redressing issues within browser form-filling features.

Attack Vector

Exploitation requires the victim to visit a crafted HTML page and perform specific UI gestures, such as clicks or focus changes on attacker-controlled elements. The attacker leverages these interactions to invoke Autofill in a manner that renders deceptive content over or near legitimate browser UI. The user may then disclose stored data, enter sensitive values into attacker-controlled fields, or trust attacker-supplied information. The vulnerability is exploitable remotely over the network through any web-accessible page.

See the Chromium Issue #360520331 and the Google Chrome Stable Update for additional technical details.

Detection Methods for CVE-2024-11111

Indicators of Compromise

  • Browser telemetry showing Chrome versions earlier than 131.0.6778.69 in active use across managed endpoints.
  • User reports of unexpected Autofill prompts or form overlays on untrusted sites.
  • Web proxy logs showing navigation to pages that trigger repeated focus or click events against hidden input fields.

Detection Strategies

  • Inventory installed Chrome versions through endpoint management and flag any build below 131.0.6778.69.
  • Correlate browser process telemetry with navigation events to identify pages abusing input focus patterns associated with Autofill invocation.
  • Monitor help-desk tickets and phishing reports for evidence of Autofill-driven credential or payment data entry on unverified domains.

Monitoring Recommendations

  • Enable centralized Chrome version reporting via Chrome Browser Cloud Management or equivalent policy tooling.
  • Forward browser and proxy logs to a centralized analytics platform to detect visits to known phishing or UI-spoofing infrastructure.
  • Track Autofill-related user complaints as a signal for ongoing social engineering campaigns targeting this class of flaw.

How to Mitigate CVE-2024-11111

Immediate Actions Required

  • Update Google Chrome to version 131.0.6778.69 or later on all desktop platforms.
  • Restart Chrome after the update to ensure the patched Autofill component is loaded.
  • Validate deployment coverage through endpoint management and quarantine hosts that remain on vulnerable builds.

Patch Information

Google released the fix in the Chrome Stable channel update published on November 12, 2024. Install 131.0.6778.69 or later on Windows, macOS, and Linux. Chromium-based browser vendors should incorporate the upstream fix referenced in Chromium Issue #360520331. Full release notes are available in the Google Chrome Stable Update announcement.

Workarounds

  • Disable Chrome Autofill for addresses, payment methods, and passwords through enterprise policy until patching is complete.
  • Train users to verify the browser address bar and avoid entering sensitive data on unfamiliar sites, especially after unexpected form interactions.
  • Enforce Safe Browsing Enhanced Protection via policy to reduce exposure to known malicious hosting infrastructure.
bash
# Example Chrome enterprise policy to disable Autofill features
# Linux: /etc/opt/chrome/policies/managed/autofill.json
{
  "AutofillAddressEnabled": false,
  "AutofillCreditCardEnabled": false,
  "PasswordManagerEnabled": false,
  "SafeBrowsingProtectionLevel": 2
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.