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-2628 Overview
CVE-2024-2628 is a user interface spoofing vulnerability in the Downloads component of Google Chrome prior to version 123.0.6312.58. A remote attacker can craft a malicious URL that manipulates how the browser renders download-related UI elements, misleading users about the origin or nature of a downloaded file. The flaw is categorized under CWE-474 and was addressed in the Chrome Stable channel update released on March 19, 2024. Chromium rates the security severity as Medium. Fedora 38, 39, and 40 also shipped updated Chromium packages to remediate the issue.
Critical Impact
Attackers can deceive users into trusting malicious downloads by spoofing the Downloads UI through a crafted URL, enabling social engineering and malware delivery.
Affected Products
- Google Chrome versions prior to 123.0.6312.58
- Fedora 38, 39, and 40 (Chromium packages)
- Chromium-based browsers consuming the upstream Downloads component
Discovery Timeline
- 2024-03-19 - Google releases Chrome Stable 123.0.6312.58 addressing the issue (Chrome Releases blog)
- 2024-03-20 - CVE-2024-2628 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-2628
Vulnerability Analysis
The vulnerability resides in the Downloads subsystem of Google Chrome, where the browser renders metadata about files initiated for download. The implementation does not correctly validate or constrain content supplied through a crafted URL. An attacker can abuse this behavior to display misleading information in the Downloads surface, such as file names, origins, or security indicators. This is classified by Chromium as a UI spoofing issue rather than a memory-safety flaw, and it requires user interaction to trigger. The issue is tracked upstream as Chromium Issue #41487774.
Root Cause
The root cause maps to CWE-474, use of a function with inconsistent implementations, applied here to the rendering logic of the Downloads UI. Specifically, the Downloads component fails to normalize or sanitize attacker-influenced URL content before presenting it to the user. This inconsistency between what the browser fetches and what it displays creates the spoofing primitive.
Attack Vector
Exploitation occurs over the network and requires the victim to visit a page controlled by the attacker or follow a malicious link. The attacker crafts a URL that drives Chrome's Downloads UI to display misleading content when a download is initiated. No authentication or elevated privileges are required. Impact is limited to integrity of the browser UI; there is no direct code execution or data confidentiality loss, but the spoof can underpin phishing and malware distribution chains.
No verified public proof-of-concept code is available. See the Chromium issue tracker for additional technical context.
Detection Methods for CVE-2024-2628
Indicators of Compromise
- Browser telemetry showing Chrome versions earlier than 123.0.6312.58 initiating downloads from newly registered or low-reputation domains.
- Downloaded files whose on-disk name or MIME type diverges from the file name presented in the browser Downloads shelf.
- Web proxy logs recording redirect chains that terminate in Content-Disposition headers with unusual or encoded file-name parameters.
Detection Strategies
- Inventory installed Chrome and Chromium builds across managed endpoints and flag any version below 123.0.6312.58.
- Correlate browser download events with process-execution telemetry to identify files that were launched immediately after a spoofed download prompt.
- Hunt for user-reported phishing lures that reference a downloaded document whose displayed source does not match the originating domain in proxy logs.
Monitoring Recommendations
- Monitor EDR file-creation events in user Downloads directories and enrich with originating URL and browser version metadata.
- Alert on executions of script interpreters or installer binaries spawned from browser-controlled Downloads paths within a short window after a navigation event.
- Track Chrome auto-update status across the fleet to confirm patch rollout and surface endpoints stuck on vulnerable builds.
How to Mitigate CVE-2024-2628
Immediate Actions Required
- Update Google Chrome to version 123.0.6312.58 or later on all managed endpoints and verify the version post-deployment.
- Apply the Fedora Chromium package updates on Fedora 38, 39, and 40 hosts via dnf update.
- Reinforce user awareness that download prompts can be manipulated and that files should be validated against the expected source before execution.
Patch Information
Google fixed CVE-2024-2628 in the Chrome Stable channel release 123.0.6312.58 for Windows, macOS, and Linux, as announced in the Stable Channel Update for Desktop. Fedora users should apply the updated Chromium packages referenced in the Fedora package announcements (FEDORA-2024 message 2D3Z6C, message 6JINDY, message AQVVW4).
Workarounds
- Enforce Chrome auto-update through enterprise policy so endpoints receive security releases without user intervention.
- Restrict download of executable file types at the web gateway and require inspection before delivery to users.
- Deploy browser isolation or SafeSearch-equivalent URL filtering for high-risk user groups until patch coverage is confirmed.
# Verify Chrome is at or above the fixed version on Linux
google-chrome --version
# Fedora: apply Chromium security updates
sudo dnf upgrade --refresh chromium
# Windows: force Chrome update check via policy registry key
reg add "HKLM\SOFTWARE\Policies\Google\Update" /v AutoUpdateCheckPeriodMinutes /t REG_DWORD /d 60 /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

