{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50238 exists.","fix":"No fix has been published for CVE-2022-50238 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-50238 is a high-severity vulnerability in Microsoft Windows, published on 8 Sep 2025. 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-50238 and fix it if it is affected.\n\nWhat it is: CVE-2022-50238 is a high-severity vulnerability in Microsoft Windows, published on 8 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50238 exists.\n\nAffected product: Microsoft Windows. 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-50238/ (Markdown: https://insights.sbomify.com/CVE-2022-50238/index.md)","id":"CVE-2022-50238","markdown":"https://insights.sbomify.com/CVE-2022-50238/index.md","name":"CVE-2022-50238","record":{"aliases":["GHSA-m379-7mfm-wqr6"],"analysis":{"component_type":"operating_system","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows OS","requires_auth":"none","summary":"The local Windows driver blocklist is outdated compared to the online list, allowing potentially vulnerable drivers to load unless WDAC policies are manually synchronized.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"},{"id":"CWE-820","name":"Missing Synchronization"}],"description":"The on-endpoint Microsoft vulnerable driver blocklist is not fully synchronized with the online Microsoft recommended driver block rules. Some entries present on the online list have been excluded from the on-endpoint blocklist longer than the expected periodic monthly Windows updates. It is possible to fully synchronize the driver blocklist using WDAC policies. NOTE: The vendor explains that Windows Update provides a smaller, compatibility-focused driver blocklist for general users, while the full XML list is available for advanced users and organizations to customize at the risk of usability issues.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in Windows","id":"CVE-2022-50238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"cpufreq: qcom: fix writes in read-only memory region","id":"CVE-2022-50239"},"packages":[],"prev":{"headline":"`ed25519-dalek` Double Public Key Signing Function Oracle Attack","id":"CVE-2022-50237"},"products":["Windows"],"published":"2025-09-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-17","vendors":["Microsoft"]},"summary":"The local Windows driver blocklist is outdated compared to the online list, allowing potentially vulnerable drivers to load unless WDAC policies are manually synchronized.","url":"https://insights.sbomify.com/CVE-2022-50238/"}