CVE-2004-0210
Microsoft Windows Privilege Escalation Vulnerability
Description
CVE-2004-0210 is a HIGH buffer copy without checking size of input ('classic buffer overflow') vulnerability affecting Microsoft Windows, carrying a CVSS 3.1 score of 7.8. A privilege elevation vulnerability exists in the POSIX subsystem. This vulnerability could allow a logged on user to take complete control of the system. Affected products include Microsoft Interix (2.2), Microsoft Windows 2000, Microsoft Windows Nt (4.0). This CVE is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog with a remediation deadline of 2022-03-24. With an EPSS score of 0.03667 (87.72th percentile), this vulnerability demonstrates significant real-world exploitation activity and should be prioritized for immediate remediation.
KEV Information
CVSS Score
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| microsoft | interix | 2.2 |
| microsoft | windows 2000 | - |
| microsoft | windows nt | 4.0 |
Multiple CVSS Assessments
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
References
- http://www.kb.cert.org/vuls/id/647436(Patch, Third Party Advisory, US Government Resource)
- http://www.us-cert.gov/cas/techalerts/TA04-196A.html(Broken Link, Patch, Third Party Advisory, US Government Resource)
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2004/ms04-020(Patch, Vendor Advisory)
- https://exchange.xforce.ibmcloud.com/vulnerabilities/16590(Third Party Advisory, VDB Entry)
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A2166(Broken Link)
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A2847(Broken Link)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2004-0210(US Government Resource)
Weakness Type
CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
CVE-2004-0210 is classified under CWE-120 — Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'). Classic Buffer Overflow is a vulnerability that occurs when a program copies data to a buffer without first checking that the data fits within the buffer's allocated size. This typically happens when functions like strcpy(), gets(), sprintf(), or memcpy() are used without proper bounds checking. When the input data exceeds the buffer capacity, it overwrites adjacent memory locations, potentially corrupting data, crashing the program, or enabling arbitrary code execution. This vulnerability class has been responsible for numerous high-profile security breaches and remains a critical concern in C/C++ applications despite decades of awareness.
In the context of Microsoft Windows, this weakness is particularly concerning because Buffer overflows are among the most dangerous vulnerabilities in software security. Attackers can exploit them to overwrite function return addresses, redirecting program execution to injected shellcode. Stack-based overflows enable reliable code execution through return-oriented programming (ROP) and other techniques that bypass modern protections like DEP/NX. Organizations using affected versions should understand that this vulnerability class has historically enabled severe compromises across enterprise environments.
Impact Analysis
CVE-2004-0210 carries a CVSS 3.1 score of 7.8 (HIGH) with Unchanged Scope.
Confidentiality (HIGH): Successful exploitation grants the attacker extensive access to sensitive data processed by Microsoft Windows, including configuration files, credentials, and potentially data from connected systems.
Integrity (HIGH): Attackers can modify critical system files, install backdoors, alter configurations, or deploy malware on affected systems running Microsoft Windows.
Availability (HIGH): Complete disruption of the affected service or system is possible, including denial of service, system crashes, or rendering the product inoperable.
Scope Unchanged: The vulnerability's scope is Unchanged (U), meaning exploitation is contained within the vulnerable component. The impact, while significant, is limited to the Microsoft Windows environment itself.
With an EPSS score of 0.03667 (87.72th percentile), this vulnerability ranks among the most likely to be exploited in real-world attacks, underscoring the urgency of remediation.
Exploit Maturity
CVE-2004-0210 has confirmed active exploitation in the wild and is listed in CISA's Known Exploited Vulnerabilities catalog.
Exploit status: This vulnerability has been actively exploited, as confirmed by its inclusion in the KEV catalog. The EPSS score of 0.03667 (87.72th percentile) places it among the most exploited vulnerabilities tracked.
Ransomware association: As of the latest KEV data, no direct ransomware association has been confirmed for CVE-2004-0210. However, the confirmed exploitation in the wild means threat actors are actively using this vulnerability in attacks.
Attack surface: While specific public exploit code may not be readily available, the vulnerability's high EPSS score and KEV listing confirm that threat actors have developed and used working exploits. Organizations should assume exploitation tools exist in underground markets and private threat actor toolkits.
KEV deadline: CISA required federal agencies to remediate this vulnerability by 2022-03-24. All organizations should treat this deadline as a strong recommendation for their own remediation timelines.
Remediation
- Apply vendor patches immediately. Apply updates per vendor instructions. Consult the vendor advisory at www.kb.cert.org for specific patch guidance.
- Verify affected product versions in your environment. Identify all instances of Microsoft Windows in your infrastructure (affected versions: Microsoft Interix (2.2), Microsoft Windows 2000, Microsoft Windows Nt (4.0)). Use asset inventory and vulnerability scanning tools to ensure no instances are missed.
- Implement interim mitigations if patching is delayed. If immediate patching is not feasible, apply network-level controls such as restricting access to the affected component, enabling enhanced logging, and monitoring for indicators of compromise.
- Scan for signs of prior exploitation. Given the confirmed active exploitation of this vulnerability, review system logs and security monitoring data for evidence of compromise. Conduct a thorough investigation if any suspicious activity is detected.
- Update detection signatures and monitoring rules. Ensure intrusion detection and prevention systems, endpoint detection tools, and SIEM rules are updated to detect exploitation attempts targeting CVE-2004-0210.
- Conduct a post-remediation review. After patching, verify the fix is effective and document the remediation actions taken. Update your vulnerability management records and assess whether any additional hardening measures are warranted.
Technical Details
CVE-2004-0210 is a HIGH-severity vulnerability in Microsoft Windows that can be exploited locally, typically requiring a user to open a malicious file or execute a malicious application. The attack complexity is low, meaning no specialized conditions or preparation are required beyond the attack prerequisites. Low-level privileges (standard user access) are required to initiate the attack. No user interaction is required, allowing fully automated exploitation once the target is accessible.
Technical mechanism: A privilege elevation vulnerability exists in the POSIX subsystem. This vulnerability could allow a logged on user to take complete control of the system. The underlying flaw relates to buffer copy without checking size of input ('classic buffer overflow'), where Classic Buffer Overflow is a vulnerability that occurs when a program copies data to a buffer without first checking that the data fits within the buffer's allocated size. This typically happens when functions like strcpy(), gets(), sprintf(), or memcpy() are used without proper bounds checking.
CVSS 3.1 vector analysis: The vector reflects an Attack Vector of LOCAL, Attack Complexity of LOW, Privileges Required of LOW, User Interaction of NONE, Scope UNCHANGED, and impact ratings of HIGH/HIGH/HIGH for Confidentiality/Integrity/Availability respectively. The Unchanged scope means impact is contained within the vulnerable component itself.
Frequently Asked Questions
What is CVE-2004-0210?
CVE-2004-0210 is a HIGH-severity vulnerability (CVSS 7.8) in Microsoft Windows that a privilege elevation vulnerability exists in the POSIX subsystem. This vulnerability could allow a logged on user to take complete control of the system. It is listed in CISA's Known Exploited Vulnerabilities catalog, confirming real-world exploitation.
Which products are affected by CVE-2004-0210?
The affected products include Microsoft Interix (2.2), Microsoft Windows 2000, Microsoft Windows Nt (4.0). Organizations running any of these versions should verify their exposure and prioritize remediation. Check vendor advisories for the complete and most current list of affected versions.
How do I fix CVE-2004-0210?
Apply updates per vendor instructions. Ensure all affected instances of Microsoft Windows are identified using vulnerability scanning and asset management tools. If immediate patching is not possible, implement network-level mitigations and enhanced monitoring. After patching, verify the fix and scan for indicators of prior compromise.
How severe is CVE-2004-0210?
CVE-2004-0210 is rated HIGH with a CVSS 3.1 score of 7.8. Its EPSS score of 0.03667 places it in the 87.72th percentile for exploitation likelihood. The vulnerability has confirmed active exploitation in the wild and was required to be remediated by federal agencies by 2022-03-24 per CISA's KEV directive.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.