dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-21284

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 10.0.10240.20890 / 10.0.14393.7699 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows Virtual Trusted Platform Module Denial of Service Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-20

The application accepts input without confirming it is well-formed or within expected bounds, so malformed data can push the program into states its author never anticipated. Attackers probe these gaps to trigger crashes, bypass logic, or feed tainted values into more dangerous operations downstream. Remediating it well means validating and normalising every input at the boundary against a strict allow-list — not merely filtering known-bad values.

General guidance for the improper input validation class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20890
Windows 10 1607Operating system
Affected:< 10.0.14393.7699
Windows 10 1809Operating system
Affected:< 10.0.17763.6775
Windows 10 21h2Operating system
Affected:< 10.0.19044.5371
Windows 10 22h2Operating system
Affected:< 10.0.19045.5371
Windows 11 22h2Operating system
Affected:< 10.0.22621.4751
Windows 11 23h2Operating system
Affected:< 10.0.22631.4751
Windows 11 24h2Operating system
Affected:< 10.0.26100.2894

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20890 / 10.0.14393.7699 / 10.0.17763.6775 or later
Fixed in 10.0.10240.2089010.0.14393.769910.0.17763.6775
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Install February 2025 Windows security update or upgrade to the fixed build number for your specific Windows version (see step 3 for build numbers)

  1. Verify current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows version family your system runs (e.g., Windows 10 22h2, Windows 11 23h2)
  3. Apply the vendor patch by installing the latest Windows security update from Microsoft Update. For CVE-2025-21284, this is included in the February 2025 or later security updates
  4. Alternatively, manually update to the fixed build number for your Windows version: Windows 10 1507 to build 10.0.10240.20890, Windows 10 1607 to build 10.0.14393.7699, Windows 10 1809 to build 10.0.17763.6775, Windows 10 21h2 to build 10.0.19044.5371, Windows 10 22h2 to build 10.0.19045.5371, Windows 11 22h2 to build 10.0.22621.4751, Windows 11 23h2 to build 10.0.22631.4751, or Windows 11 24h2 to
  5. Restart the system as prompted to complete the update
  6. Confirm the vulnerability is remediated by checking that the build number matches or exceeds the fixed version for your Windows release
Caveat Standard security update - may require system restart; no significant breaking changes expected

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21284 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21284 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data