CVE-2024-10668

7.5 HIGH

📋 TL;DR

This vulnerability allows attackers to bypass Google Quick Share's file validation by sending duplicate file transfer frames, enabling them to upload arbitrary files to victims' Downloads folders. It affects Windows users running vulnerable versions of Google Quick Share. Attackers can exploit this to deliver malicious files that would normally be blocked.

💻 Affected Systems

Products:
  • Google Quick Share (formerly Nearby Share)
Versions: Versions before commit 5d8b9156e0c339d82d3dab0849187e8819ad92c0 or Quick Share Windows v1.0.2002.2
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Requires Quick Share to be enabled and receiving files. The vulnerability is in the file handling logic when receiving duplicate file transfers.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers deliver malware, ransomware, or other malicious executables directly to victims' systems, leading to full system compromise, data theft, or encryption.

🟠

Likely Case

Attackers deliver phishing documents, scripts, or other malicious files that users might accidentally execute, leading to limited system compromise or credential theft.

🟢

If Mitigated

With proper endpoint protection and user awareness, malicious files are detected before execution, limiting impact to file system clutter.

🌐 Internet-Facing: MEDIUM - Requires proximity-based Bluetooth/Wi-Fi Direct connection, not directly internet-accessible but can be exploited in public spaces.
🏢 Internal Only: MEDIUM - Attackers on same network could exploit if Quick Share is enabled, but requires specific conditions.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires sending specially crafted duplicate file transfer frames via Bluetooth/Wi-Fi Direct. No authentication needed once connection is established.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Quick Share Windows v1.0.2002.2 or later

Vendor Advisory: https://github.com/google/nearby/pull/2892

Restart Required: Yes

Instructions:

1. Open Google Chrome. 2. Go to chrome://flags. 3. Search for 'Quick Share'. 4. Ensure it's updated to v1.0.2002.2+. 5. Restart Chrome. Alternatively, update through Windows Store if installed as standalone app.

🔧 Temporary Workarounds

Disable Quick Share

windows

Temporarily disable Quick Share file receiving to prevent exploitation

Open Chrome → Settings → Advanced → Privacy and security → Site settings → Nearby Share → Disable

Restrict Downloads Folder Permissions

windows

Set Downloads folder to read-only or require admin approval for executions

Right-click Downloads folder → Properties → Security → Edit permissions → Deny write/execute for standard users

🧯 If You Can't Patch

  • Disable Quick Share entirely until patching is possible
  • Implement application whitelisting to prevent execution of unknown files from Downloads folder

🔍 How to Verify

Check if Vulnerable:

Check Quick Share version in Chrome flags (chrome://flags search 'Quick Share') or Windows Store. If version is below v1.0.2002.2, system is vulnerable.

Check Version:

In Chrome: chrome://flags then search 'Quick Share'. In Windows: Get-AppxPackage *QuickShare* | Select Version

Verify Fix Applied:

Confirm version is v1.0.2002.2 or higher. Test by attempting to send duplicate file transfers (if safe testing environment available).

📡 Detection & Monitoring

Log Indicators:

  • Multiple file write events with same payload ID in Quick Share logs
  • Unexpected files appearing in Downloads folder from Quick Share transfers

Network Indicators:

  • Unusual Bluetooth/Wi-Fi Direct connections followed by duplicate file transfer patterns

SIEM Query:

EventID=4663 AND ObjectName LIKE '%Downloads%' AND ProcessName LIKE '%chrome.exe%' AND AccessMask='0x100' AND Count>1 within 5 seconds

🔗 References

📤 Share & Export