dbcve.org
Windows Server 2016Operating system · Microsoft

CVE-2024-26233

MEDIUM · 6.6 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 10.0.14393.6897 / 10.0.17763.5696 or later.
See remediation →
72/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
Windows DNS Server Remote Code Execution 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

This is a Remote Code Execution vulnerability in Windows DNS Server. The vulnerability allows an attacker to execute arbitrary code on affected Windows DNS Server installations. Given the CVSS score of 6.6 (MEDIUM), it likely requires some level of access or specific conditions to exploit.

MitigationApply the relevant Microsoft security updates for Windows DNS Server. Until patches are applied, consider network segmentation to limit exposure of DNS servers to untrusted networks and implement monitoring for anomalous DNS traffic patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 2016Operating system
Affected:< 10.0.14393.6897
Windows Server 2019Operating system
Affected:< 10.0.17763.5696
Windows Server 2022Operating system
Affected:< 10.0.20348.2402
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.830

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

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify DNS Server role is installed
    Run 'Get-WindowsFeature -Name DNS' in PowerShell on the target server, or check via Server Manager > Add Roles and Features > DNS Server
    Affected if DNS Server role is installed - without this role, the server is not vulnerable to this specific flaw
  2. Check Windows Server build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the build number, or use 'Get-ComputerInfo | Select-Object WindowsVersion,OsBuildNumber' in PowerShell
    Affected if Build number falls below the fixed versions: < 14393.6897 (Server 2016), < 17763.5696 (Server 2019), < 20348.2402 (Server 2022), or < 25398.830 (Server 2022 23h2)
  3. Confirm DNS Server service is running
    Run 'Get-Service -Name DNS' or 'sc query DNS' to check if the DNS Server service (named "DNS Server") is active
    Affected if DNS Server service is running - exploitation requires the DNS Server service to be enabled and operational

A server is affected if it runs a Windows Server 2016/2019/2022 variant with the DNS Server role installed, the DNS Server service is active, and the build version is below the fixed thresholds listed above.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.6897 / 10.0.17763.5696 / 10.0.20348.2402 or later
Fixed in 10.0.14393.689710.0.17763.569610.0.20348.2402
Interim mitigation

Apply the relevant Microsoft security updates for Windows DNS Server. Until patches are applied, consider network segmentation to limit exposure of DNS servers to untrusted networks and implement monitoring for anomalous DNS traffic patterns.

Recommended fix High confidence

Windows Server 2016: 10.0.14393.6897 | Windows Server 2019: 10.0.17763.5696 | Windows Server 2022: 10.0.20348.2402 | Windows Server 2022 23h2: 10.0.25398.830

  1. Open Settings on the Windows Server and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to scan for available patches
  3. Locate the security update corresponding to CVE-2024-26233 (typically labeled with the CVE ID or the month it was released)
  4. Click 'Download' or 'Install' to apply the update
  5. After installation completes, restart the server when prompted to ensure the patch takes effect
  6. Verify the update was successfully installed by running 'winver' or checking the Windows Update history to confirm the version matches or exceeds: 10.0.14393.6897 (Server 2016), 10.0.17763.5696 (Server 2019), 10.0.20348.2402 (Server 2022), or 10.0.25398.830 (Server 2022 23h2)
Caveat Standard Windows security update; no breaking changes expected; schedule downtime for the required restart

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

Fix this in Windows Server 2016 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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