{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15001 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15001 is a medium-severity missing authorization vulnerability in n/a, published on 9 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-15001 and fix it if it is affected.\n\nWhat it is: CVE-2020-15001 is a medium-severity missing authorization vulnerability in n/a, published on 9 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-15001 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-15001/ (Markdown: https://insights.sbomify.com/CVE-2020-15001/index.md)","id":"CVE-2020-15001","markdown":"https://insights.sbomify.com/CVE-2020-15001/index.md","name":"CVE-2020-15001","record":{"aliases":["GHSA-9wfp-32vx-wv8g"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"YubiKey 5 NFC","requires_auth":"none","summary":"Attackers can bypass access codes to read OTPs and passwords from NFC slots on YubiKey 5 devices.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yubikey_5_nfc_firmware","vendor":"yubico"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"An information leak was discovered on Yubico YubiKey 5 NFC devices 5.0.0 to 5.2.6 and 5.3.0 to 5.3.1. The OTP application allows a user to set optional access codes on OTP slots. This access code is intended to prevent unauthorized changes to OTP configurations. The access code is not checked when updating NFC specific components of the OTP configurations. This may allow an attacker to access configured OTPs and passwords stored in slots that were not configured by the user to be read over NFC, despite a user having set an access code. (Users who have not set an access code, or who have not configured the OTP slots, are not impacted by this issue.)","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":"Missing authorization in n/a","id":"CVE-2020-15001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2020-15002"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-15000"},"products":["n/a"],"published":"2020-07-09","related":[{"cvss_score":5.9,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-15000","kev_date_added":null,"published":"2020-07-09"}],"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 bypass access codes to read OTPs and passwords from NFC slots on YubiKey 5 devices.","url":"https://insights.sbomify.com/CVE-2020-15001/"}