LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50238: The on-endpoint Microsoft vulnerable driver blocklist is not fully synchronized with the online Microsoft r...

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.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Windows may not automatically receive Microsoft’s full recommended vulnerable driver block rules. Some organizations may believe Windows Update fully synchronizes the online list, but the source says the on-endpoint list can remain smaller for compatibility reasons.

Executive priority

Prioritize as endpoint hardening for Windows 10 fleets, especially higher-risk workstations and servers. It is not documented here as actively exploited, but the gap weakens expected protection against vulnerable drivers.

Technical view

CVE-2022-50238 describes incomplete synchronization between the on-endpoint Microsoft vulnerable driver blocklist and Microsoft’s online recommended driver block rules. The listed vector is local, high complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

The bundle identifies Microsoft Windows 10. Exposure is most likely where endpoints rely only on the default Windows Update driver blocklist instead of managed WDAC policy synchronization.

Exploitation context

No cited source or KEV status supports active exploitation. The risk is local and high complexity, but impact is high if driver-blocking gaps are abused.

Researcher notes

Evidence describes a synchronization and compatibility tradeoff, not a specific vulnerable driver. Microsoft’s note says Windows Update provides a smaller compatibility-focused list, while the full XML list is available for advanced customization.

Mitigation direction

  • Review Microsoft’s recommended driver block rules for applicability.
  • Test WDAC policies that synchronize the fuller driver blocklist.
  • Pilot enforcement on representative hardware for compatibility impact.
  • Do not assume Windows Update contains the full online list.
  • Monitor Microsoft guidance for blocklist behavior changes.

Validation and detection

  • Inventory Windows 10 endpoints and driver-blocking configuration.
  • Compare endpoint coverage with Microsoft’s recommended driver block rules.
  • Confirm WDAC deployment and enforcement state on pilot systems.
  • Document compatibility exceptions and approved deviations.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-184: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-820: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-50238 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H1.45.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2022-50238Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows10unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-184 · source CWE mapping

Incomplete List of Disallowed Inputs

Incomplete List of Disallowed Inputs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-820 · source CWE mapping

Missing Synchronization

Missing Synchronization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.