dbcve.org
Windows 11 21h2Operating system · Microsoft

CVE-2024-43584

HIGH · 8.4 CVSS v3.1 Published 2024-10-08
Fix available
A fix is available. Upgrade to 10.0.20348.2762 / 10.0.22000.3260 or later.
See remediation →
89/100
Remediation priority · High
No privileges 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 Scripting Engine Security Feature Bypass 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

A detailed technical summary for this CVE is being prepared.

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 11 21h2Operating system
Affected:< 10.0.22000.3260
Windows 11 22h2Operating system
Affected:< 10.0.22621.4317
Windows 11 23h2Operating system
Affected:< 10.0.22631.4317
Windows 11 24h2Operating system
Affected:< 10.0.26100.2033
Windows Server 2022Operating system
Affected:< 10.0.20348.2762
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1189

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.20348.2762 / 10.0.22000.3260 / 10.0.22621.4317 or later
Fixed in 10.0.20348.276210.0.22000.326010.0.22621.4317
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Windows 11 21h2: 10.0.22000.3260 | Windows 11 22h2: 10.0.22621.4317 | Windows 11 23h2: 10.0.22631.4317 | Windows 11 24h2: 10.0.26100.2033 | Windows Server 2022: 10.0.20348.2762 | Windows Server 2022 23h2: 10.0.25398.1189

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify the specific Windows edition and version (21h2, 22h2, 23h2, 24h2, or Server 2022/Server 2022 23h2) from the version number
  3. Navigate to Windows Update: Settings > Update & Security > Windows Update
  4. Click 'Check for updates' to receive the security patch for CVE-2024-43584
  5. Alternatively, manually download the specific KB patch from the Microsoft Update Catalog for your Windows version
  6. Install the update and restart the system when prompted
  7. Verify the update was installed successfully by checking Windows Update history or running 'systeminfo' to confirm the build number matches or exceeds the fixed version for your release
Caveat Standard Windows security update; no major breaking changes expected; test Line of Business applications after patching as a best practice

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,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43584 — 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-2024-43584 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