# CVE-2019-1213: Windows DHCP Server Remote Code Execution Vulnerability

> An attacker can execute arbitrary code on Windows Server DHCP by sending specially crafted network packets.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/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:** 14 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7j2x-4f39-6gwm

## What is CVE-2019-1213?

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

### Official description

A memory corruption vulnerability exists in the Windows Server DHCP service when an attacker sends specially crafted packets to a DHCP server. An attacker who successfully exploited the vulnerability could run arbitrary code on the DHCP server.
To exploit the vulnerability, an attacker could send a specially crafted packet to a DHCP server.
The security update addresses the vulnerability by correcting how DHCP servers handle network packets.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-1213?

It affects 1 product.


Products: Microsoft Windows Server 2008.

## How do I fix CVE-2019-1213?

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

## Is CVE-2019-1213 being exploited?

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

## 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-2019-1213 and fix it if it is affected.

What it is: CVE-2019-1213 is a critical memory corruption vulnerability in Microsoft Windows Server 2008, published on 14 Aug 2019. 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-2019-1213 exists.

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-2019-1213/ (Markdown: https://insights.sbomify.com/CVE-2019-1213/index.md)
```

## Sources

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

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