dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2024-30036

MEDIUM · 6.5 CVSS v3.1 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
Windows Deployment Services Information Disclosure 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 an information disclosure vulnerability in Windows Deployment Services (WDS). WDS is a server role used for network-based installation of Windows operating systems. The vulnerability allows an attacker to potentially access sensitive information that should not be normally accessible, likely related to deployment configurations, images, or credentials stored within the WDS environment.

MitigationApply the Microsoft security update for CVE-2024-30036 through Windows Update or your organization's patch management system. Verify that network access to Windows Deployment Services is restricted to authorized administrators only.

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 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

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
High
Integrity
None
Availability
None

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

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 Windows Deployment Services role is installed
    Open Server Manager, go to Manage > Remove Roles and Features, or run Get-WindowsFeature -Name WDS in PowerShell to list installed roles
    Affected if Windows Deployment Services is installed and enabled on the server
  2. Identify the installed Windows Server version and build number
    Run 'winver' from command prompt, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in command prompt, or run [System.Environment]::OSVersion.Version in PowerShell
    Affected if Server is running a version within the affected ranges (Server 2008/2012 any version, Server 2016 build < 14393.6981, Server 2019 build < 17763.5820, Server 2022 build < 20348.2461)
  3. Check the exact build number for Windows Server 2016, 2019, or 2022
    Run 'winver' or check the output of 'systeminfo' to obtain the full build number (for example 10.0.14393.xxxx) and compare it against the specific threshold for your server version
    Affected if Build number is lower than 10.0.14393.6981 (Server 2016), 10.0.17763.5820 (Server 2019), or 10.0.20348.2461 (Server 2022)
  4. Confirm WDS service status
    Open Services console (services.msc) or run Get-Service WDS, WDSServer in PowerShell to verify the Windows Deployment Services service is running
    Affected if WDS service is installed and running on an affected Windows Server version

The server is affected if Windows Deployment Services is installed on any version of Windows Server 2008, 2012, or on Windows Server 2016/2019/2022 with a build number below the specified thresholds.

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.6981 / 10.0.17763.5820 / 10.0.20348.2461 or later
Fixed in 10.0.14393.698110.0.17763.582010.0.20348.2461
Interim mitigation

Apply the Microsoft security update for CVE-2024-30036 through Windows Update or your organization's patch management system. Verify that network access to Windows Deployment Services is restricted to authorized administrators only.

Recommended fix High confidence

Install the appropriate Windows cumulative security update containing the CVE-2024-30036 fix; for WS2016 use build 10.0.14393.6981 or later, WS2019 use build 10.0.17763.5820 or later, WS2022 use build 10.0.20348.2461 or later; for WS2008/2012 contact Microsoft for extended support options

  1. Open Windows Update on the affected Windows Server
  2. Check for and install the latest cumulative security updates
  3. Specifically, install the KB that addresses CVE-2024-30036 (check Microsoft Update Catalog for the specific KB number for your Windows Server version)
  4. Restart the server if prompted
  5. Verify the update was installed successfully by checking installed updates
Caveat Standard Windows update risks apply - test updates in staging environment before production deployment; some updates may require restart

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

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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