{"answers":{"affected":"It affects 10 products.","exploited":"There is no known exploitation of CVE-2020-8341 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8341 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8341 is a low-severity vulnerability in Lenovo ThinkPad, published on 1 Sep 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-8341 and fix it if it is affected.\n\nWhat it is: CVE-2020-8341 is a low-severity vulnerability in Lenovo ThinkPad, published on 1 Sep 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-8341 in the wild and no public exploit code.\n\nAffected product: Lenovo ThinkPad. 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-8341/ (Markdown: https://insights.sbomify.com/CVE-2020-8341/index.md)","id":"CVE-2020-8341","markdown":"https://insights.sbomify.com/CVE-2020-8341/index.md","name":"CVE-2020-8341","record":{"aliases":["GHSA-f46h-7c54-hvw7"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Lenovo ThinkPad BIOS","requires_auth":"none","summary":"An attacker could bypass secondary SPI flash protection mechanisms on Lenovo ThinkPads after sleep, though primary SMM protection remains active.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"lenovo","cpe":[{"product":"thinkpad_t490_\\(20nx\\)_firmware","vendor":"lenovo"},{"product":"thinkpad_t490_\\(20qx\\)_firmware","vendor":"lenovo"},{"product":"thinkpad_t490_\\(20rx\\)_firmware","vendor":"lenovo"},{"product":"thinkpad_t490s_\\(20nx\\)_firmware","vendor":"lenovo"},{"product":"thinkpad_t495_drift_firmware","vendor":"lenovo"},{"product":"thinkpad_t590_\\(20nx\\)_firmware","vendor":"lenovo"},{"product":"thinkpad_x1_carbon_\\(20qx\\)_firmware","vendor":"lenovo"},{"product":"thinkpad_x1_yoga_\\(20qx\\)_firmware","vendor":"lenovo"},{"product":"thinkpad_x390_\\(20qx\\)_firmware","vendor":"lenovo"},{"product":"thinkpad_x390_\\(20sx\\)_firmware","vendor":"lenovo"}],"cvss":{"score":2.4,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash. While this provides sufficient protection, an additional layer of protection is provided by SPI Protected Range Registers (PRx). After resuming from S3 sleep mode in various versions of BIOS for some Lenovo ThinkPad systems, the PRx is not set. This does not impact the SMM BIOS Write Protection, which keeps systems protected.","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 ThinkPad","id":"CVE-2020-8341","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in System Update","id":"CVE-2020-8342"},"packages":[],"prev":{"headline":"Cross-site scripting in System x IMM2 firmware","id":"CVE-2020-8340"},"products":["ThinkPad"],"published":"2020-09-01","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-16","vendors":["Lenovo"]},"summary":"An attacker could bypass secondary SPI flash protection mechanisms on Lenovo ThinkPads after sleep, though primary SMM protection remains active.","url":"https://insights.sbomify.com/CVE-2020-8341/"}