{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10876 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10876 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10876 is a high-severity authentication bypass 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-10876 and fix it if it is affected.\n\nWhat it is: CVE-2020-10876 is a high-severity authentication bypass 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-10876 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-10876/ (Markdown: https://insights.sbomify.com/CVE-2020-10876/index.md)","id":"CVE-2020-10876","markdown":"https://insights.sbomify.com/CVE-2020-10876/index.md","name":"CVE-2020-10876","record":{"aliases":["GHSA-7hrr-hhcx-cw5q"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Bluetooth padlock app","requires_auth":"none","summary":"Attackers can brute force verification codes to bypass email checks and take over user accounts in the OKLOK mobile app.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"oklok","vendor":"oklok_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"},{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"The OKLOK (3.1.1) mobile companion app for Fingerprint Bluetooth Padlock FB50 (2.3) does not correctly implement its timeout on the four-digit verification code that is required for resetting passwords, nor does it properly restrict excessive verification attempts. This allows an attacker to brute force the four-digit verification code in order to bypass email verification and change the password of a victim account.","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":"Auth bypass in n/a","id":"CVE-2020-10876","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in n/a","id":"CVE-2020-10878"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2020-10875"},"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":6.5,"headline":"Missing authorization in n/a","id":"CVE-2020-8791","kev_date_added":null,"published":"2020-05-04"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2020-8792","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":"Attackers can brute force verification codes to bypass email checks and take over user accounts in the OKLOK mobile app.","url":"https://insights.sbomify.com/CVE-2020-10876/"}