CVE-2004-0840 in the critical feed json
The SMTP (Simple Mail Transfer Protocol) component of Microsoft Windows XP 64-bit Edition, Windows Server 2003, Windows Server 2003 64-bit…
published 2004-10-16 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0838
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 30.2%
- EPSS 30.2% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
The SMTP (Simple Mail Transfer Protocol) component of Microsoft Windows XP 64-bit Edition, Windows Server 2003, Windows Server 2003 64-bit Edition, and the Exchange Routing Engine component of Exchange Server 2003, allows remote attackers to execute arbitrary code via a malicious DNS response message containing length values that are not properly validated.
Patch / fix
Exploit prediction
30.15% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2004/ms04-035
vendor-advisory, patch
-
kb.cert.org
/vuls/id/394792
third-party-advisory, patch, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A2300
vdb-entry, signature, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5509
vdb-entry, signature, third-party-advisory
-
securityfocus.com
/bid/11374
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/17660
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/17621
vdb-entry, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A3460
vdb-entry, signature, third-party-advisory
Sources
- CVE List CVE-2004-0840
- NVD CVE-2004-0840
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.