{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30283 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30283 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30283 is a high-severity vulnerability in n/a, published on 15 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-30283 and fix it if it is affected.\n\nWhat it is: CVE-2022-30283 is a high-severity vulnerability in n/a, published on 15 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-30283 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-30283/ (Markdown: https://insights.sbomify.com/CVE-2022-30283/index.md)","id":"CVE-2022-30283","markdown":"https://insights.sbomify.com/CVE-2022-30283/index.md","name":"CVE-2022-30283","record":{"aliases":["GHSA-24pw-pfmp-w2w4"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"InsydeH2O firmware","requires_auth":"high_privilege","summary":"An attacker can exploit a TOCTOU race condition in USB firmware to corrupt SMRAM and escalate privileges.","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.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"In UsbCoreDxe, tampering with the contents of the USB working buffer using DMA while certain USB transactions are in process leads to a TOCTOU problem that could be used by an attacker to cause SMRAM corruption and escalation of privileges The UsbCoreDxe module creates a working buffer for USB transactions outside of SMRAM. The code which uses can be inside of SMM, making the working buffer untrusted input. The buffer can be corrupted by DMA transfers. The SMM code code attempts to sanitize pointers to ensure all pointers refer to the working buffer, but when a pointer is not found in the list of pointers to sanitize, the current action is not aborted, leading to undefined behavior. This issue was discovered by Insyde engineering based on the general description provided by Intel's iSTARE group. Fixed in: Kernel 5.0: Version 05.09. 21 Kernel 5.1: Version 05.17.21 Kernel 5.2: Version 05.27.21 Kernel 5.3: Version 05.36.21 Kernel 5.4: Version 05.44.21 Kernel 5.5: Version 05.52.21 https://www.insyde.com/security-pledge/SA-2022063","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-30283","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":"Argument injection in python-libnmap","id":"CVE-2022-30284"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2022-30280"},"products":["n/a"],"published":"2022-11-15","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":"total"},"state":"PUBLISHED","updated":"2025-04-30","vendors":["n/a"]},"summary":"An attacker can exploit a TOCTOU race condition in USB firmware to corrupt SMRAM and escalate privileges.","url":"https://insights.sbomify.com/CVE-2022-30283/"}