dbcve.org
Windows Server 2012Operating system · Microsoft

CVE-2024-49091

HIGH · 7.2 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 10.0.14393.7606 / 10.0.17763.6659 or later.
See remediation →
78/100
Remediation priority · High
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 Domain Name Service 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 · moderate confidence

This is a remote code execution vulnerability in Windows Domain Name Service (DNS). An attacker could potentially execute arbitrary code on affected Windows systems running the DNS Server service, likely by sending specially crafted DNS queries or leveraging DNS protocol handling flaws.

MitigationApply the Microsoft security update for CVE-2024-49091. If immediate patching is not possible, consider restricting network access to DNS servers and implementing DNS traffic monitoring for anomalous activity.

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 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7606
Windows Server 2019Operating system
Affected:< 10.0.17763.6659
Windows Server 2022Operating system
Affected:< 10.0.20348.2966
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1308
Windows Server 2025Operating system
Affected:< 10.0.26100.2605

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

CVSS:3.1/AV:N/AC:L/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 or check via Server Manager > Add Roles and Features > DNS Server under Server Roles
    Affected if DNS Server role is installed or the DNS service (dns.exe) is present on the system
  2. Confirm DNS Server service is running
    Run 'Get-Service -Name DNS' or check Task Manager for dns.exe process
    Affected if DNS Server service is running (status shows 'Running')
  3. Identify Windows Server version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows Server build number
    Affected if The displayed build number falls below the fixed version for your specific Windows Server release
  4. Compare build number against affected ranges
    Note the full build number (e.g., 10.0.14393.xxxx) and compare: Server 2016 < 7606, Server 2019 < 6659, Server 2022 < 2966, Server 2022 23h2 < 1308, Server 2025 < 2605. Server 2012 is fully affected.
    Affected if Your build number is lower than the threshold for your Windows Server version, or you are on Windows Server 2012/R2 (all versions)

You are affected if you are running Windows Server 2012/R2 with DNS Server role, or any Windows Server 2016/2019/2022/2025 variant with a build number below the fixed threshold and the DNS Server service is enabled.

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.7606 / 10.0.17763.6659 / 10.0.20348.2966 or later
Fixed in 10.0.14393.760610.0.17763.665910.0.20348.2966
Interim mitigation

Apply the Microsoft security update for CVE-2024-49091. If immediate patching is not possible, consider restricting network access to DNS servers and implementing DNS traffic monitoring for anomalous activity.

Recommended fix High confidence

Upgrade to the specified build numbers: Windows Server 2016 (10.0.14393.7606+), Server 2019 (10.0.17763.6659+), Server 2022 (10.0.20348.2966+), Server 2022 23h2 (10.0.25398.1308+), Server 2025 (10.0.26100.2605+); migrate from EOL Server 2012/2012R2 to supported version

  1. 1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. For Windows Server 2016: Upgrade to build 10.0.14393.7606 or later (install Windows Server 2016 Cumulative Update)
  3. 3. For Windows Server 2019: Upgrade to build 10.0.17763.6659 or later (install Windows Server 2019 Cumulative Update)
  4. 4. For Windows Server 2022: Upgrade to build 10.0.20348.2966 or later (install Windows Server 2022 Cumulative Update)
  5. 5. For Windows Server 2022 23h2: Upgrade to build 10.0.25398.1308 or later
  6. 6. For Windows Server 2025: Upgrade to build 10.0.26100.2605 or later
  7. 7. For Windows Server 2012/2012 R2: These versions are end-of-life; migrate to a supported Windows Server version (2016 or later)
  8. 8. Apply updates via Windows Update, WSUS, or download from Microsoft Update Catalog
Caveat Windows Server 2012 and 2012 R2 are end-of-life with no patches; requires full OS migration; standard cumulative update apply may require restart and should be tested in non-production first

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

Fix this in Windows Server 2012 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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