{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-26556 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2020-26556 is a high-severity authentication bypass vulnerability in n/a, published on 24 May 2021. 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-26556 and fix it if it is affected.\n\nWhat it is: CVE-2020-26556 is a high-severity authentication bypass vulnerability in n/a, published on 24 May 2021. 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-26556 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-26556/ (Markdown: https://insights.sbomify.com/CVE-2020-26556/index.md)","id":"CVE-2020-26556","markdown":"https://insights.sbomify.com/CVE-2020-26556/index.md","name":"CVE-2020-26556","record":{"aliases":["GHSA-69j7-838h-x496","ROOT-OS-UBUNTU-2204-CVE-2020-26556","UBUNTU-CVE-2020-26556"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bluetooth Mesh stack","requires_auth":"none","summary":"A nearby attacker can bypass Bluetooth Mesh provisioning authentication by brute-forcing weak AuthValues due to malleable commitments.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bluetooth_core_specification","vendor":"bluetooth"},{"product":"mesh_profile","vendor":"bluetooth"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, able to conduct a successful brute-force attack on an insufficiently random AuthValue before the provisioning procedure times out, to complete authentication by leveraging Malleable Commitment.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Auth bypass in n/a","id":"CVE-2020-26556","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2020-26557"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2020-26555"},"products":["n/a"],"published":"2021-05-24","related":[{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2022-25836","kev_date_added":null,"published":"2022-12-12"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2022-25837","kev_date_added":null,"published":"2022-12-12"},{"cvss_score":6.4,"headline":"Weak cryptography in n/a","id":"CVE-2023-24023","kev_date_added":null,"published":"2023-11-28"},{"cvss_score":5.9,"headline":"Auth bypass in n/a","id":"CVE-2020-15802","kev_date_added":null,"published":"2020-09-11"},{"cvss_score":5.4,"headline":"Auth bypass in n/a","id":"CVE-2020-26555","kev_date_added":null,"published":"2021-05-24"},{"cvss_score":5.3,"headline":"Race condition in n/a","id":"CVE-2021-31615","kev_date_added":null,"published":"2021-06-25"}],"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":"A nearby attacker can bypass Bluetooth Mesh provisioning authentication by brute-forcing weak AuthValues due to malleable commitments.","url":"https://insights.sbomify.com/CVE-2020-26556/"}