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-3841 Overview
CVE-2024-3841 is an input validation flaw in the Browser Switcher component of Google Chrome prior to version 124.0.6367.60. The vulnerability stems from insufficient data validation, allowing a remote attacker to inject scripts or HTML into a privileged Chrome page through a malicious file. Google's Chromium team rated the security severity as Medium. The weakness is tracked under [CWE-79] (Cross-Site Scripting) and [CWE-20] (Improper Input Validation). Successful exploitation requires user interaction, such as opening or processing a crafted file.
Critical Impact
Attackers can inject arbitrary scripts or HTML into a Chrome privileged page, breaking browser isolation boundaries and potentially escalating access to sensitive browser internals.
Affected Products
- Google Chrome versions prior to 124.0.6367.60
- Microsoft Windows (Chrome Browser Switcher is Windows-specific)
- Fedora 38, 39, and 40 distributions shipping affected Chromium builds
Discovery Timeline
- 2024-04-17 - CVE-2024-3841 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-3841
Vulnerability Analysis
The Browser Switcher (also known as Legacy Browser Support) is a Chrome enterprise feature that redirects specific URLs from Chrome to a legacy browser such as Internet Explorer. The component parses configuration and site list data and renders portions of that data in a Chrome-internal privileged page. Insufficient data validation in this rendering path allows attacker-controlled content sourced from a malicious file to reach the DOM of a privileged page without proper sanitization. Because privileged pages run with elevated capabilities compared to standard web content, injected scripts execute outside the normal web sandbox boundary. The flaw is classified as both [CWE-79] Cross-Site Scripting and [CWE-20] Improper Input Validation.
Root Cause
The root cause is missing or incomplete sanitization of untrusted data before it is inserted into a Chrome privileged page owned by the Browser Switcher feature. When file-sourced input flows into HTML rendering primitives without escaping or a strict Content Security Policy, script and markup payloads execute in the page context. Google addressed the issue in Chrome 124.0.6367.60 by hardening validation in the Browser Switcher code path.
Attack Vector
Exploitation is network-adjacent and requires user interaction. An attacker crafts a malicious file consumable by the Browser Switcher configuration or URL-processing logic and delivers it to a targeted user through phishing, a compromised update channel, or an attacker-controlled enterprise policy source. When Chrome processes the file, injected HTML or JavaScript executes in the context of the privileged Browser Switcher page, enabling script injection, UI spoofing, and potential access to browser-privileged APIs. See the Chromium Issue Tracker Entry and the Chrome Stable Update Announcement for release context.
Detection Methods for CVE-2024-3841
Indicators of Compromise
- Chrome executables reporting a version older than 124.0.6367.60 in enterprise inventory scans.
- Unexpected files or policy artifacts referenced by the Browser Switcher configuration path on Windows endpoints.
- Chrome renderer processes loading unusual privileged page URLs (chrome://browser-switch/) following file access events.
Detection Strategies
- Inventory installed Chrome versions across managed endpoints and flag any build below 124.0.6367.60.
- Monitor Group Policy Object (GPO) and registry keys under HKLM\Software\Policies\Google\Chrome\BrowserSwitcher* for unauthorized changes to site lists or executable paths.
- Alert on Chrome processes spawning legacy browser binaries with unusual command-line arguments sourced from untrusted policy files.
Monitoring Recommendations
- Enable Chrome Enterprise reporting to centralize browser version and policy telemetry.
- Correlate endpoint file-write events on Browser Switcher configuration files with subsequent Chrome activity.
- Track EPSS movement for CVE-2024-3841, currently 0.73% at percentile 52.449, as an exploitation-likelihood signal.
How to Mitigate CVE-2024-3841
Immediate Actions Required
- Update Google Chrome to 124.0.6367.60 or later on all Windows endpoints where Browser Switcher may be enabled.
- Apply Fedora Chromium updates referenced in the Fedora Package Announcement for Fedora 38, 39, and 40.
- Audit and restrict the source of Browser Switcher policy and site list files to trusted administrators only.
Patch Information
Google released the fix in Chrome Stable channel version 124.0.6367.60 on Windows, Mac, and Linux. Details are documented in the Chrome Stable Update Announcement. Fedora shipped corresponding Chromium package updates for Fedora 38, 39, and 40 through the Fedora package-announce mailing list.
Workarounds
- Disable the Browser Switcher feature via the BrowserSwitcherEnabled policy set to false where legacy browser redirection is not required.
- Restrict write permissions on Browser Switcher site list and executable path locations to prevent tampering by non-administrative users.
- Enforce Chrome auto-update to reduce the window of exposure on unmanaged endpoints.
# Configuration example: disable Chrome Browser Switcher via Windows registry
reg add "HKLM\Software\Policies\Google\Chrome" /v BrowserSwitcherEnabled /t REG_DWORD /d 0 /f
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

