{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11539 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11539 is a high-severity missing authorization vulnerability in n/a, published on 22 Apr 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-11539 and fix it if it is affected.\n\nWhat it is: CVE-2020-11539 is a high-severity missing authorization vulnerability in n/a, published on 22 Apr 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-11539 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-11539/ (Markdown: https://insights.sbomify.com/CVE-2020-11539/index.md)","id":"CVE-2020-11539","markdown":"https://insights.sbomify.com/CVE-2020-11539/index.md","name":"CVE-2020-11539","record":{"aliases":["GHSA-grfx-46mw-p6mw"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smart fitness band","requires_auth":"none","summary":"Attackers can intercept unencrypted data and control device parameters due to lack of Bluetooth pairing and authentication.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sf_rush_smart_band_firmware","vendor":"titan"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"An issue was discovered on Tata Sonata Smart SF Rush 1.12 devices. It has been identified that the smart band has no pairing (mode 0 Bluetooth LE security level) The data being transmitted over the air is not encrypted. Adding to this, the data being sent to the smart band doesn't have any authentication or signature verification. Thus, any attacker can control a parameter of the device.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-02-05","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-02-05T12:19:19Z","kind":"github_poc","ref":"https://github.com/the-girl-who-lived/CVE-2020-11539","stars":1,"title":"Improper Access Control in Tata Sonata Smartband"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2020-11539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"XML external entity in n/a","id":"CVE-2020-11541"},"packages":[],"prev":{"headline":"Out-of-bounds read in Pillow","id":"CVE-2020-11538"},"products":["n/a"],"published":"2020-04-22","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)"},{"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 intercept unencrypted data and control device parameters due to lack of Bluetooth pairing and authentication.","url":"https://insights.sbomify.com/CVE-2020-11539/"}