# CVE-2024-38077: Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability

> An attacker can execute arbitrary code on Windows Server systems via the Remote Desktop Licensing Service due to a heap-based buffer overflow.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 9 Jul 2024
- **Updated:** 10 Feb 2026
- **Also known as:** GHSA-9j79-xcx5-mxm4

## What is CVE-2024-38077?

CVE-2024-38077 is a critical memory corruption vulnerability in Microsoft Windows Server 2008, published on 9 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 6 products.


Products: 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.

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

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

## Is CVE-2024-38077 being exploited?

There is no known exploitation of CVE-2024-38077 in the wild and no public exploit code.

Public exploit code:

- RDL的堆溢出导致的RCE (github_poc): https://github.com/qi4L/CVE-2024-38077
- CVE-2024-38077: Remote Code Execution Vulnerability in Windows Remote Desktop Licensing Service (github_poc): https://github.com/mrmtwoj/CVE-2024-38077
- 远程探测 remote desktop licensing 服务开放情况，用于 CVE-2024-38077 漏洞快速排查 (github_poc): https://github.com/murphysecurity/RDL-detect
- https://github.com/SecStarBot/CVE-2024-38077-POC (github_poc): https://github.com/SecStarBot/CVE-2024-38077-POC
- 检测RDL服务是否运行，快速排查受影响资产 (github_poc): https://github.com/zhuxi1965/CVE-2024-38077-RDLCheck
- CVE-2024-38077,仅支持扫描测试~ (github_poc): https://github.com/BBD-YZZ/fyne-gui

## Other vulnerabilities in Microsoft Windows Server 2008

- [CVE-2020-1350](https://insights.sbomify.com/CVE-2020-1350/): Microsoft Windows DNS Server Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2020-1040](https://insights.sbomify.com/CVE-2020-1040/): Microsoft Hyper-V RemoteFX vGPU Remote Code Execution (critical 9.0, exploited in the wild)
- [CVE-2011-1966](https://insights.sbomify.com/CVE-2011-1966/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0239](https://insights.sbomify.com/CVE-2010-0239/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0240](https://insights.sbomify.com/CVE-2010-0240/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38077 is a critical memory corruption vulnerability in Microsoft Windows Server 2008, published on 9 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38077 in the wild and no public exploit code.

Affected product: Microsoft Windows Server 2008. 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-38077/ (Markdown: https://insights.sbomify.com/CVE-2024-38077/index.md)
```

## Sources

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

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