Skip to main content

CVE-2024-8907: Google Chrome Omnibox XSS Vulnerability

CVE-2024-8907 is a cross-site scripting vulnerability in Google Chrome's Omnibox on Android that allows attackers to inject malicious scripts through UI manipulation. This article covers technical details, affected versions, and mitigation.

Published:

CVE-2024-8907 Overview

CVE-2024-8907 is a cross-site scripting (XSS) vulnerability in the Omnibox component of Google Chrome on Android. The flaw stems from insufficient data validation in versions prior to 129.0.6668.58. A remote attacker can inject arbitrary scripts or HTML by convincing a user to perform a specific set of user interface (UI) gestures. Chromium security engineers rated the issue Medium severity. The weakness maps to Improper Neutralization of Input During Web Page Generation [CWE-79].

Critical Impact

Successful exploitation allows attackers to inject arbitrary scripts or HTML into the browser context, enabling session theft, credential harvesting, or delivery of follow-on payloads through a crafted page combined with user gestures.

Affected Products

  • Google Chrome on Android prior to 129.0.6668.58
  • Google Android platform (Chrome browser distribution)
  • Chromium-based browsers on Android that consume vulnerable Omnibox code

Discovery Timeline

  • 2024-09-17 - CVE-2024-8907 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-8907

Vulnerability Analysis

The vulnerability resides in the Omnibox, the combined address and search bar in Chrome for Android. Omnibox processes user-entered URLs, search terms, and suggestion data drawn from remote sources. Insufficient validation of that data allowed attacker-controlled content to reach a rendering context where it was interpreted as active markup or script.

Because the flaw requires user interaction (UI:R) and a specific sequence of UI gestures, exploitation depends on social engineering. When triggered, the injected content runs within a scope that can affect resources beyond the originally loaded origin, reflected in the changed scope metric (S:C). Impact is limited to partial confidentiality and integrity loss, with no direct availability impact.

Root Cause

The underlying defect is improper neutralization of input rendered through the Omnibox UI pipeline. Data that should have been treated strictly as text was accepted into a context where HTML or script parsing occurred. This is a canonical [CWE-79] pattern applied to a browser chrome component rather than a traditional web page.

Attack Vector

Exploitation is network-based. An attacker hosts a crafted web resource and guides the victim through a defined series of Omnibox interactions, such as tapping, copying, or interacting with URL suggestions. The gesture sequence causes Chrome to render attacker-controlled markup, producing an XSS condition in the browser context. No verified public proof-of-concept or in-the-wild exploitation has been reported. See the Chromium Issue Tracker Entry and the Google Chrome Desktop Update for release context.

Detection Methods for CVE-2024-8907

Indicators of Compromise

  • Android devices running Chrome versions earlier than 129.0.6668.58 browsing to untrusted or newly registered domains.
  • Unusual JavaScript execution or DOM changes tied to Omnibox suggestion interactions rather than page loads.
  • Outbound requests to attacker infrastructure originating immediately after specific Omnibox gesture patterns.

Detection Strategies

  • Inventory Chrome for Android versions across managed mobile devices and flag installations below the patched build.
  • Monitor Mobile Device Management (MDM) telemetry for Chrome app version drift and delayed Play Store updates.
  • Correlate web proxy logs with mobile user-agent strings to identify vulnerable clients reaching high-risk domains.

Monitoring Recommendations

  • Track Google Play update compliance for Chrome across enterprise Android fleets.
  • Alert on Android browser sessions that establish connections to newly observed domains hosting phishing or social engineering content.
  • Review Safe Browsing and URL filtering logs for repeated user interaction with suspect Omnibox suggestion sources.

How to Mitigate CVE-2024-8907

Immediate Actions Required

  • Update Google Chrome on Android to 129.0.6668.58 or later through the Google Play Store.
  • Enforce mandatory browser updates via Mobile Device Management (MDM) policies on corporate Android devices.
  • Reinforce user awareness on avoiding untrusted links and unexpected Omnibox interaction prompts.

Patch Information

Google released the fix in Chrome 129.0.6668.58 for Android. Refer to the Google Chrome Desktop Update advisory covering the 129 stable channel release. Detailed defect information is tracked in the Chromium Issue Tracker Entry.

Workarounds

  • Restrict use of Chrome on Android to updated builds only; block older versions through MDM compliance policies.
  • Deploy enterprise URL filtering to reduce exposure to attacker-controlled pages that could trigger the gesture sequence.
  • Advise users to avoid interacting with Omnibox suggestions that appear after visiting untrusted sites until patching is confirmed.

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

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

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.