Unknown-file placement via duplicate payload IDs
Published Nov 7, 2024 · Updated Nov 21, 2024
File upload validation bypass in Google Quick Share before 1.0.2002.2 allows attackers to place an unknown file in Downloads. OnPayloadReceived writes both files for two FILE frames that reuse one payload ID, while the later unknown-type cleanup deletes only the first. The attack requires adjacent access, low privileges, and active user interaction; it leaves a normally rejected file on Windows but does not itself establish execution.
Summary
What happened
File upload validation bypass in Google Quick Share before 1.0.2002.2 allows attackers to place an unknown file in Downloads. OnPayloadReceived writes both files for two FILE frames that reuse one payload ID, while the later unknown-type cleanup deletes only the first. The attack requires adjacent access, low privileges, and active user interaction; it leaves a normally rejected file on Windows but does not itself establish execution.
The record
- CVE
- CVE-2024-10668
- Published
- Nov 7, 2024
- Updated
- Nov 21, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, CAPEC-165, T1105
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 7, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo