dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2024-30019

MEDIUM · 6.5 CVSS v3.1 Developing Published 2024-05-14
Fix available
A fix is available. Upgrade to 10.0.14393.6981 / 10.0.17763.5820 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
DHCP Server Service 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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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 Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.6981
Windows Server 2019Operating system
Affected:< 10.0.17763.5820
Windows Server 2022Operating system
Affected:< 10.0.20348.2461
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.887

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

CVSS:3.1/AV:N/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.14393.6981 / 10.0.17763.5820 / 10.0.20348.2461 or later
Fixed in 10.0.14393.698110.0.17763.582010.0.20348.2461
Recommended fix High confidence

Apply the relevant Windows Server security update (e.g., KB5034123 for WS2019) to reach fixed build versions: 10.0.14393.6981 (WS2016), 10.0.17763.5820 (WS2019), 10.0.20348.2461 (WS2022), 10.0.25398.887 (WS2022 23h2)

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine the applicable update by checking the Windows Server version against the affected version ranges in the CVE
  3. Apply the relevant security update from Microsoft Update Catalog or Windows Update for the specific Windows Server version (e.g., for Windows Server 2019, apply KB5034123 or subsequent security updates)
  4. Restart the DHCP Server service or reboot the server as required by the applied update
  5. Verify the patch was successfully installed by checking the installed updates via 'Get-HotFix' in PowerShell or reviewing the Windows Update history
  6. Confirm the DHCP Server service is running and the version matches or exceeds the fixed build numbers (10.0.14393.6981 for WS2016, 10.0.17763.5820 for WS2019, 10.0.20348.2461 for WS2022, 10.0.25398.887 for WS2022 23h2)
Caveat Standard Windows security update; may require service restart or server reboot; no breaking changes expected for this DoS vulnerability patch

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-2024-30019 — 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-30019 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