Security readout for executives and security teams
Plain-English summary
This issue affects Microsoft Windows NT 4.0 DHCP Server when DHCP logging is enabled. A malformed DHCP message can crash the DHCP service, disrupting address assignment for users and systems. The source bundle does not show code execution, data theft, CVSS scoring, or confirmed active exploitation.
Executive priority
Prioritize this if any Windows NT 4.0 DHCP infrastructure remains in production. The business risk is service disruption, not documented compromise. If no affected legacy DHCP servers exist, this should be tracked as historical cleanup rather than an urgent incident.
Technical view
CVE-2004-0899 is a length-validation flaw in the DHCP Server service on Microsoft Windows NT 4.0 Server and Terminal Server Edition with DHCP logging enabled. Remote malformed DHCP traffic can trigger an application crash, causing denial of service. Public sources identify MS04-042 and OVAL checks, but the bundle provides no exploit-status details.
Likely exposure
Exposure is likely limited to legacy environments still running Windows NT 4.0 DHCP Server or Terminal Server Edition with DHCP logging enabled. Modern Windows DHCP deployments are not identified in the supplied sources as affected.
Exploitation context
The bundle says remote attackers can cause a DHCP service crash with malformed DHCP messages. CISA KEV status is false, and no cited source in the bundle confirms active exploitation or public weaponization.
Researcher notes
The source bundle is sparse: no CVSS vector, CWE, detailed affected CPEs, or exploit telemetry are provided. Analysis should stay anchored to MS04-042, the CVE description, IBM X-Force, and OVAL definitions rather than extrapolating to other Windows versions.
Mitigation direction
- Review Microsoft MS04-042 and apply the vendor-provided security update where applicable.
- Identify and retire Windows NT 4.0 DHCP servers where operationally possible.
- Restrict DHCP service exposure to trusted local network segments.
- Review whether DHCP logging is enabled on legacy Windows NT DHCP servers.
- Maintain tested DHCP redundancy or recovery procedures for affected legacy networks.
Validation and detection
- Inventory DHCP servers and confirm operating system versions.
- Check for Windows NT 4.0 Server or Terminal Server Edition DHCP roles.
- Verify whether DHCP logging is enabled on any affected host.
- Confirm MS04-042 remediation status using vendor or OVAL guidance.
- Review monitoring for DHCP service crashes or unexpected restarts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2004-0899 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- winnt-dhcp-machinename-dos(18341)CVE reference · vdb-entry, x_refsource_XF
- oval:org.mitre.oval:def:4282CVE reference · vdb-entry, signature
- oval:org.mitre.oval:def:2280CVE reference · vdb-entry, signature
- MS04-042CVE reference · vendor-advisory, x_refsource_MS
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
