{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2002-2059 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-2059 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-2059 is a medium-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2002-2059 and fix it if it is affected.\n\nWhat it is: CVE-2002-2059 is a medium-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2002-2059 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-2002-2059/ (Markdown: https://insights.sbomify.com/CVE-2002-2059/index.md)","id":"CVE-2002-2059","markdown":"https://insights.sbomify.com/CVE-2002-2059/index.md","name":"CVE-2002-2059","record":{"aliases":["GHSA-rhp3-rf73-5hpc"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Intel motherboard BIOS","requires_auth":"none","summary":"Local users can bypass BIOS password restrictions to change the boot device via the F8 key on affected Intel motherboards.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"d845bg_motherboard","vendor":"intel"},{"product":"d845hv_motherboard","vendor":"intel"},{"product":"d845pt_motherboard","vendor":"intel"},{"product":"d845wn_motherboard","vendor":"intel"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"BIOS D845BG, D845HV, D845PT and D845WN on Intel motherboards does not properly restrict access to configuration information when BIOS passwords are enabled, which could allow local users to change the default boot device via the F8 key.","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":"Security feature bypass in n/a","id":"CVE-2002-2059","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2002"},"n_packages":0,"n_references":8,"next":{"headline":"Memory corruption in n/a","id":"CVE-2002-2060"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2002-2058"},"products":["n/a"],"published":"2005-07-14","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Local users can bypass BIOS password restrictions to change the boot device via the F8 key on affected Intel motherboards.","url":"https://insights.sbomify.com/CVE-2002-2059/"}