{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8792 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8792 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8792 is a medium-severity vulnerability in n/a, published on 4 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-8792 and fix it if it is affected.\n\nWhat it is: CVE-2020-8792 is a medium-severity vulnerability in n/a, published on 4 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-8792 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-8792/ (Markdown: https://insights.sbomify.com/CVE-2020-8792/index.md)","id":"CVE-2020-8792","markdown":"https://insights.sbomify.com/CVE-2020-8792/index.md","name":"CVE-2020-8792","record":{"aliases":["GHSA-9g78-xvpc-6fhg"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Bluetooth padlock app","requires_auth":"none","summary":"The OKLOK mobile app discloses user email addresses and lock names when adding already-bound locks via predictable barcodes.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"oklok","vendor":"oklok_project"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"The OKLOK (3.1.1) mobile companion app for Fingerprint Bluetooth Padlock FB50 (2.3) has an information-exposure issue. In the mobile app, an attempt to add an already-bound lock by its barcode reveals the email address of the account to which the lock is bound, as well as the name of the lock. Valid barcode inputs can be easily guessed because barcode strings follow a predictable pattern. Correctly guessed valid barcode inputs entered through the app interface disclose arbitrary users' email addresses and lock names.","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-8792","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2020-8793"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-8791"},"products":["n/a"],"published":"2020-05-04","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-8790","kev_date_added":null,"published":"2020-05-04"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2020-10876","kev_date_added":null,"published":"2020-05-04"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2020-8791","kev_date_added":null,"published":"2020-05-04"}],"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":"The OKLOK mobile app discloses user email addresses and lock names when adding already-bound locks via predictable barcodes.","url":"https://insights.sbomify.com/CVE-2020-8792/"}