Full Report
Microsoft acknowledged a new issue caused by the June 2025 security updates, causing the DHCP service to freeze on some Windows Server systems. [...]
Analysis Summary
Since the provided article discusses a *consequence* of the June Windows Server security updates (DHCP issues) and references *previous* issues resolved by other updates (unreachable domain controllers, Hyper-V issues, container launch issues), but **does not specify a new CVE or a specific patch designed to fix the *new* DHCP problem**, the summary must reflect that the details for the *current* reported issue are missing.
# Vulnerability: Unspecified DHCP Issue Following June Windows Server Updates
## CVE Details
- CVE ID: Not specified in the context provided. The issue appears to be a regression/bug introduced by recent cumulative updates, not a newly disclosed vulnerability with an assigned CVE.
- CVSS Score: Not available.
- CWE: Not applicable/Unknown (Likely a functional/regression bug rather than a standard security flaw).
## Affected Systems
- Products: Windows Server (Implied, specifically systems receiving the June 2025 cumulative updates).
- Versions: Unspecified, but tied to the deployment of the June 2025 security updates.
- Configurations: Systems running the DHCP service after applying the relevant June updates.
## Vulnerability Description
Microsoft acknowledged that certain Windows Server security updates released in June 2025 have caused issues related to the Dynamic Host Configuration Protocol (DHCP). The nature of the fault is that the application or functionality related to DHCP is impaired following the installation of these updates. (The article focuses more on troubleshooting the side effect than detailing the specific technical flaw causing the DHCP failure.)
## Exploitation
- Status: Not applicable. This is an operational bug/regression introduced by a patch, not a traditional security vulnerability being exploited.
- Complexity: Not applicable.
- Attack Vector: Not applicable.
## Impact
- Confidentiality: Unknown, likely Low (unless DHCP failure is leveraged for a secondary attack).
- Integrity: Unknown, potentially Moderate (Service degradation due to lack of IP assignment).
- Availability: High (If DHCP service fails, new devices cannot obtain network configuration, impacting availability).
## Remediation
### Patches
- Specific patch information for the **July 2025 or later** update addressing the DHCP issue is **not available** in this context compilation.
### Workarounds
- No specific workarounds for this new DHCP issue are detailed in the provided text.
- **Implicit Workaround:** Removal or rollback of the June 2025 cumulative update if the DHCP service is critical and required immediate restoration, though this carries security risks. (Note: Microsoft often releases subsequent emergency/out-of-band fixes for regressions).
## Detection
- Indicators of Compromise: Failures in DHCP scope lease negotiation, servers/clients unable to obtain IP addresses, or DHCP service errors logged.
- Detection methods and tools: Monitoring DHCP service health and event logs on affected Windows Servers.
## References
- Vendor advisories: Microsoft Advisory regarding June 2025 Windows Server updates causing DHCP issues.
- Relevant links - defanged:
- bleepingcomputer.com/news/microsoft/microsoft-june-windows-server-security-updates-cause-dhcp-issues/