{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3432 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-3432 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3432 is a medium-severity vulnerability in Lenovo BIOS, published on 23 Jan 2023. 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-2022-3432 and fix it if it is affected.\n\nWhat it is: CVE-2022-3432 is a medium-severity vulnerability in Lenovo BIOS, published on 23 Jan 2023. 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-2022-3432 in the wild and no public exploit code.\n\nAffected product: Lenovo BIOS. 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-2022-3432/ (Markdown: https://insights.sbomify.com/CVE-2022-3432/index.md)","id":"CVE-2022-3432","markdown":"https://insights.sbomify.com/CVE-2022-3432/index.md","name":"CVE-2022-3432","record":{"aliases":["GHSA-w8r4-jpw4-3xhr"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Lenovo BIOS","requires_auth":"high_privilege","summary":"An attacker with elevated privileges can bypass Secure Boot by modifying NVRAM variables via a leftover manufacturing driver in Lenovo BIOS.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"lenovo","cpe":[{"product":"ideapad_y700-14isk_firmware","vendor":"lenovo"}],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"A potential vulnerability in a driver used during manufacturing process on the Ideapad Y700-14ISK that was mistakenly not deactivated may allow an attacker with elevated privileges to modify secure boot setting by modifying an NVRAM variable.","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 BIOS","id":"CVE-2022-3432","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in aeson","id":"CVE-2022-3433"},"packages":[],"prev":{"headline":"Security feature bypass in BIOS","id":"CVE-2022-3431"},"products":["BIOS"],"published":"2023-01-23","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-01","vendors":["Lenovo"]},"summary":"An attacker with elevated privileges can bypass Secure Boot by modifying NVRAM variables via a leftover manufacturing driver in Lenovo BIOS.","url":"https://insights.sbomify.com/CVE-2022-3432/"}