{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35693 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35693 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35693 is a high-severity vulnerability in Google Android, published on 24 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-35693 and fix it if it is affected.\n\nWhat it is: CVE-2020-35693 is a high-severity vulnerability in Google Android, published on 24 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-35693 in the wild and no public exploit code.\n\nAffected product: Google Android. 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-2020-35693/ (Markdown: https://insights.sbomify.com/CVE-2020-35693/index.md)","id":"CVE-2020-35693","markdown":"https://insights.sbomify.com/CVE-2020-35693/index.md","name":"CVE-2020-35693","record":{"aliases":["GHSA-cm97-fwp9-pfjj"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Android BLE","requires_auth":"none","summary":"Attackers can silently pair with vulnerable Samsung devices via BLE to steal identity keys, enabling long-term user tracking without interaction.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"android","vendor":"google"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"On some Samsung phones and tablets running Android through 7.1.1, it is possible for an attacker-controlled Bluetooth Low Energy (BLE) device to pair silently with a vulnerable target device, without any user interaction, when the target device's Bluetooth is on, and it is running an app that offers a connectable BLE advertisement. An example of such an app could be a Bluetooth-based contact tracing app, such as Australia's COVIDSafe app, Singapore's TraceTogether app, or France's TousAntiCovid (formerly StopCovid). As part of the pairing process, two pieces (among others) of personally identifiable information are exchanged: the Identity Address of the Bluetooth adapter of the target device, and its associated Identity Resolving Key (IRK). Either one of these identifiers can be used to perform re-identification of the target device for long term tracking. The list of affected devices includes (but is not limited to): Galaxy Note 5, Galaxy S6 Edge, Galaxy A3, Tab A (2017), J2 Pro (2018), Galaxy Note 4, and Galaxy S5.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2020-35693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-35698"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-35687"},"products":["n/a"],"published":"2020-12-24","related":[{"cvss_score":8.8,"headline":"Google Pixel Improper Authorization","id":"CVE-2026-58704","kev_date_added":"2026-09-16","published":"2026-09-15"},{"cvss_score":8.8,"headline":"Android Runtime Use-After-Free","id":"CVE-2025-48543","kev_date_added":"2025-09-04","published":"2025-09-04"},{"cvss_score":8.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2023-35674","kev_date_added":"2023-09-13","published":"2023-09-11"},{"cvss_score":8.4,"headline":"Android Framework Integer Overflow","id":"CVE-2025-48595","kev_date_added":"2026-06-02","published":"2026-06-01"},{"cvss_score":8.1,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-32896","kev_date_added":"2024-06-13","published":"2024-06-13"},{"cvss_score":7.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2025-48572","kev_date_added":"2025-12-02","published":"2025-12-08"},{"cvss_score":7.8,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-29748","kev_date_added":"2024-04-04","published":"2024-04-05"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can silently pair with vulnerable Samsung devices via BLE to steal identity keys, enabling long-term user tracking without interaction.","url":"https://insights.sbomify.com/CVE-2020-35693/"}