CVE-2025-29954
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 · uneditedUncontrolled resource consumption in Windows LDAP - Lightweight Directory Access Protocol allows an unauthorized attacker to deny service over a network.
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 confidenceCVE-2025-29954 is a denial-of-service vulnerability in Windows LDAP (Lightweight Directory Access Protocol) stemming from uncontrolled resource consumption. An unauthenticated remote attacker can exploit this vulnerability over the network to cause a DoS condition, potentially disrupting directory services that rely on LDAP for authentication and authorization.
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< 10.0.10240.21014< 10.0.14393.8066< 10.0.17763.7314< 10.0.19044.5854< 10.0.19045.5854< 10.0.22621.5335< 10.0.22631.5335all versions= r2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if LDAP service is running or exposedRun 'netstat -an | findstr "389 636"' to see if LDAP ports (389 for LDAP, 636 for LDAPS) are listening, or check LDAP-related services via Services.mscAffected if LDAP ports 389 or 636 are listening - the vulnerability requires the LDAP service to be exposed on the network
-
Determine Windows version and build numberRun 'winver' or 'systeminfo' to obtain the exact OS version and build number (for example, 10.0.19045.5854)Affected if The installed version falls below any of these thresholds: Windows 10 1507 < 10.0.10240.21014, Windows 10 1607 < 10.0.14393.8066, Windows 10 1809 < 10.0.17763.7314, Windows 10 21h2 < 10.0.19044.5854, Windows 10 22h2 < 10.0.19045.5854, Windows 11 22h2 < 10.0.22621.5335, Windows 11 23h2 < 10.0.22631.5
-
Confirm LDAP server role is installedCheck if the Active Directory Domain Services or LDAP service role is installed via 'Get-WindowsFeature | Where-Object {$_.Name -like "*LDAP*" -or $_.Name -like "*AD-Domain*"}' or Server ManagerAffected if The LDAP server role (Active Directory Domain Services) is installed and running, making the system a potential target for network-based LDAP DoS attacks
A system is affected if it runs any unpatched Windows version within the affected ranges AND has LDAP services (ports 389/636) exposed on the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2101410.0.14393.806610.0.17763.7314
Apply the relevant Microsoft security patches for this vulnerability to all affected Windows systems running LDAP services. Implement network-level rate limiting and monitoring on LDAP ports (389/636) to detect anomalous request patterns.
Upgrade to the specific build number for your Windows release (e.g., Windows 10 22h2 to build 10.0.19045.5854 or later; Windows 11 23h2 to build 10.0.22631.5335 or later)
- 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
- 2. Determine which Windows 10 or 11 version family your system is running (1507, 1607, 1809, 21h2, 22h2, 11 22h2, or 11 23h2)
- 3. Navigate to Windows Update Settings or use the Microsoft Update Catalog at https://www.catalog.update.microsoft.com/
- 4. Search for and install the security update corresponding to your Windows version that addresses CVE-2025-29954
- 5. For Windows 10 1507: Install update to reach build 10.0.10240.21014 or later
- 6. For Windows 10 1607: Install update to reach build 10.0.14393.8066 or later
- 7. For Windows 10 1809: Install update to reach build 10.0.17763.7314 or later
- 8. For Windows 10 21h2: Install update to reach build 10.0.19044.5854 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-29954 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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