CVE-2024-30098

Windows Cryptographic Services Security Feature Bypass Vulnerability

HIGH
7.5
CVSS Score
Published: July 9, 2024 at 05:02 PM UTC
Updated: June 17, 2026 at 07:26 AM UTC
16 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows Server 2025 (Server Core installation) by Microsoft?

Get instant alerts when new vulnerabilities affect Windows Server 2025 (Server Core installation) - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 1%
SSVC
No known exploit

Description

Windows Cryptographic Services Security Feature Bypass Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.10240.2071010.0.10240.0 ≤ v < 10.0.10240.2116110.0.10240.0
Affected range stops below 10.0.10240.20710, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.10240.21161, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.715910.0.14393.0 ≤ v < 10.0.14393.851910.0.14393.0
Affected range stops below 10.0.14393.7159, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.14393.8519, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.605410.0.17763.0 ≤ v < 10.0.17763.791910.0.17763.0
Affected range stops below 10.0.17763.6054, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.17763.7919, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.465110.0.19044.0 ≤ v < 10.0.19044.645610.0.19044.0
Affected range stops below 10.0.19044.4651, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.19044.6456, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.465110.0.19045.0 ≤ v < 10.0.19045.645610.0.19045.0
Affected range stops below 10.0.19045.4651, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.19045.6456, so it looks safe — our inference, not a vendor statement
v < 10.0.22000.307910.0.22000.0 ≤ v < 10.0.22000.307910.0.22000.0
Affected range stops below 10.0.22000.3079, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.388010.0.22621.0 ≤ v < 10.0.22621.606010.0.22621.0
Affected range stops below 10.0.22621.3880, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.22621.6060, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.388010.0.22631.0 ≤ v < 10.0.22631.606010.0.22631.0
Affected range stops below 10.0.22631.3880, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.22631.6060, so it looks safe — our inference, not a vendor statement
6.3.9600.0 ≤ v < 6.3.9600.228246.3.9600.0r2
Affected range stops below 6.3.9600.22824, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.715910.0.14393.0 ≤ v < 10.0.14393.851910.0.14393.0
Affected range stops below 10.0.14393.7159, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.14393.8519, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-327NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card