# CVE-2024-49113: Windows Lightweight Directory Access Protocol (LDAP) Denial of Service Vulnerability

> An attacker can cause a denial of service in Windows LDAP by exploiting an out-of-bounds read vulnerability.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2024
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-hq8w-cr85-pwqw

## What is CVE-2024-49113?

CVE-2024-49113 is a high-severity denial of service vulnerability in Microsoft Windows 10 1507, published on 10 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Windows Lightweight Directory Access Protocol (LDAP) Denial of Service Vulnerability

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-49113?

It affects 14 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 22h2, Microsoft Windows 11 24h2, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2024-49113?

No fix has been published for CVE-2024-49113 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-49113 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49113 exists.

Public exploit code:

- LdapNightmare is a PoC tool that tests a vulnerable Windows Server against CVE-2024-49113 (github_poc): https://github.com/SafeBreach-Labs/CVE-2024-49113
- https://github.com/barcrange/CVE-2024-49113-Checker (github_poc): https://github.com/barcrange/CVE-2024-49113-Checker
- Hi, This is to check targets vulnerable for CVE-2024-49113 in bulk, faster. (github_poc): https://github.com/Sachinart/CVE-2024-49113-Checker
- FYP: Reproduced CVE-2024-49113 PoC on Windows Server 2019 (ref. SafeBreach); assessed Windows EDR detection gaps and produced ISO 27001-aligned remediation report. (github_poc): https://github.com/alphatin123/CVE-2024-49113
- SafeBreaches CVE-2024-49113 POC(LdapNightmare) Integrated into Metasploit (github_poc): https://github.com/0xMetr0/metasploit-ldapnightmare
- Reproduction of cve-2024-49113-ldap_nightmare_reproduction (github_poc): https://github.com/razureink/cve-2024-49113-ldap_nightmare_reproduction

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49113 and fix it if it is affected.

What it is: CVE-2024-49113 is a high-severity denial of service vulnerability in Microsoft Windows 10 1507, published on 10 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49113 exists.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-49113/ (Markdown: https://insights.sbomify.com/CVE-2024-49113/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-49113
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-49113
- OSV: https://osv.dev/vulnerability/CVE-2024-49113

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-49113/
Summaries are generated and may contain mistakes; the official description above is the record.