{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-33909 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-33909 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-33909 is a high-severity vulnerability in n/a, published on 14 Nov 2022. 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-33909 and fix it if it is affected.\n\nWhat it is: CVE-2022-33909 is a high-severity vulnerability in n/a, published on 14 Nov 2022. 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-33909 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-2022-33909/ (Markdown: https://insights.sbomify.com/CVE-2022-33909/index.md)","id":"CVE-2022-33909","markdown":"https://insights.sbomify.com/CVE-2022-33909/index.md","name":"CVE-2022-33909","record":{"aliases":["GHSA-473j-fxxv-6h26"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Insyde BIOS firmware","requires_auth":"low_privilege","summary":"Attackers can corrupt SMRAM via a TOCTOU race condition in the HddPassword driver, potentially gaining elevated privileges or executing code.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kernel","vendor":"insyde"}],"cvss":{"score":7,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"DMA transactions which are targeted at input buffers used for the HddPassword software SMI handler could cause SMRAM corruption through a TOCTOU attack. DMA transactions which are targeted at input buffers used for the software SMI handler used by the HddPassword driver could cause SMRAM corruption through a TOCTOU attack..This issue was discovered by Insyde engineering based on the general description provided by Intel's iSTARE group. Fixed in kernel Kernel 5.2: 05.27.23, Kernel 5.3: 05.36.23, Kernel 5.4: 05.44.23, Kernel 5.5: 05.52.23 https://www.insyde.com/security-pledge/SA-2022051","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":"Race condition in n/a","id":"CVE-2022-33909","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"MantisBT XSS through crafted SVG documents in file_download.php","id":"CVE-2022-33910"},"packages":[],"prev":{"headline":"Race condition in n/a","id":"CVE-2022-33908"},"products":["n/a"],"published":"2022-11-14","related":[{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-36337","kev_date_added":null,"published":"2022-11-23"},{"cvss_score":8.2,"headline":"Privilege escalation in n/a","id":"CVE-2022-29275","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-29276","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-29278","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-29279","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-30771","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-30772","kev_date_added":null,"published":"2022-11-15"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-04-30","vendors":["n/a"]},"summary":"Attackers can corrupt SMRAM via a TOCTOU race condition in the HddPassword driver, potentially gaining elevated privileges or executing code.","url":"https://insights.sbomify.com/CVE-2022-33909/"}