{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-14292 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14292 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-14292 is a medium-severity vulnerability in n/a, published on 9 Sep 2020. 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-2020-14292 and fix it if it is affected.\n\nWhat it is: CVE-2020-14292 is a medium-severity vulnerability in n/a, published on 9 Sep 2020. 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-2020-14292 in the wild and no public exploit code.\n\nAffected product: n/a. 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-14292/ (Markdown: https://insights.sbomify.com/CVE-2020-14292/index.md)","id":"CVE-2020-14292","markdown":"https://insights.sbomify.com/CVE-2020-14292/index.md","name":"CVE-2020-14292","record":{"aliases":["GHSA-h3cc-g2jj-55gh"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"COVIDSafe Android app","requires_auth":"none","summary":"Attackers can reveal the victim's public Bluetooth address by tricking the app into using BR/EDR transport, bypassing address randomization protections.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"covidsafe","vendor":"health"}],"cvss":{"score":5.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"In the COVIDSafe application through 1.0.21 for Android, unsafe use of the Bluetooth transport option in the GATT connection allows attackers to trick the application into establishing a connection over Bluetooth BR/EDR transport, which reveals the public Bluetooth address of the victim's phone without authorisation, bypassing the Bluetooth address randomisation protection in the user's phone.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-08-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-08-20T05:24:30Z","kind":"github_poc","ref":"https://github.com/alwentiu/CVE-2020-14292","stars":0,"title":"Details of CVE-2020-14292"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2020-14292","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Command injection in n/a","id":"CVE-2020-14293"},"packages":[],"prev":{"headline":"Other in HCL Commerce","id":"CVE-2020-14275"},"products":["n/a"],"published":"2020-09-09","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-12857","kev_date_added":null,"published":"2020-05-18"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-12858","kev_date_added":null,"published":"2020-05-18"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2020-12859","kev_date_added":null,"published":"2020-05-18"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2020-12860","kev_date_added":null,"published":"2020-05-18"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can reveal the victim's public Bluetooth address by tricking the app into using BR/EDR transport, bypassing address randomization protections.","url":"https://insights.sbomify.com/CVE-2020-14292/"}