{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-10668 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-10668 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-10668 is a medium-severity vulnerability in Google Nearby, published on 7 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-10668 and fix it if it is affected.\n\nWhat it is: CVE-2024-10668 is a medium-severity vulnerability in Google Nearby, published on 7 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-10668 in the wild and no public exploit code.\n\nAffected product: Google Nearby. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-10668/ (Markdown: https://insights.sbomify.com/CVE-2024-10668/index.md)","id":"CVE-2024-10668","markdown":"https://insights.sbomify.com/CVE-2024-10668/index.md","name":"CVE-2024-10668","record":{"aliases":["GHSA-j9g6-vvr6-x5wm"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Google Quick Share","requires_auth":"low_privilege","summary":"An attacker can bypass file deletion logic to upload malicious files to a victim's Downloads folder, potentially leading to code execution.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"quick_share","vendor":"google"}],"cvss":{"score":5.9,"severity":"medium","source":"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","version":"4.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Auth Bypass in Quickshare","id":"CVE-2024-10668","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Countdown Timer block – Display the event's date into a timer. \u003c= 1.2.4 - Authenticated (Contributor+) Post Disclosure","id":"CVE-2024-10669"},"packages":[],"prev":{"headline":"Information disclosure in Content Slider Block – Slide Through Text or Media Content","id":"CVE-2024-10667"},"products":["Nearby"],"published":"2024-11-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-21","vendors":["Google"]},"summary":"An attacker can bypass file deletion logic to upload malicious files to a victim's Downloads folder, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2024-10668/"}