{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-15509 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15509 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15509 is a medium-severity vulnerability in n/a, published on 7 Jul 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-15509 and fix it if it is affected.\n\nWhat it is: CVE-2020-15509 is a medium-severity vulnerability in n/a, published on 7 Jul 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-15509 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-15509/ (Markdown: https://insights.sbomify.com/CVE-2020-15509/index.md)","id":"CVE-2020-15509","markdown":"https://insights.sbomify.com/CVE-2020-15509/index.md","name":"CVE-2020-15509","record":{"aliases":["GHSA-4jg3-fc9f-gv94"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android BLE Library","requires_auth":"none","summary":"Attackers can intercept Bluetooth Low Energy communications because the library falsely reports encryption during bond creation, exposing sensitive data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"android_ble_library","vendor":"nordicsemi"},{"product":"dfu_library","vendor":"nordicsemi"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"Nordic Semiconductor Android BLE Library through 2.2.1 and DFU Library through 1.10.4 for Android (as used by nRF Connect and other applications) can engage in unencrypted communication while showing the user that the communication is purportedly encrypted. The problem is in bond creation (e.g., internalCreateBond in BleManagerHandler).","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":"Security feature bypass in n/a","id":"CVE-2020-15509","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2020-15511"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2020-15507"},"products":["n/a"],"published":"2020-07-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can intercept Bluetooth Low Energy communications because the library falsely reports encryption during bond creation, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2020-15509/"}