CVE-2003-0820 in the critical feed json
Microsoft Word 97, 98(J), 2000, and 2002, and Microsoft Works Suites 2001 through 2004, do not properly check the length of the "Macro name…
published 2003-11-18 22 y ago modified 2026-06-16 4 mo ago also EUVD-2003-0811
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 26.3%
- EPSS 26.3% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Microsoft Word 97, 98(J), 2000, and 2002, and Microsoft Works Suites 2001 through 2004, do not properly check the length of the "Macro names" data value, which could allow remote attackers to execute arbitrary code via a buffer overflow attack.
Patch / fix
- securityfocus.com/bid/8835 advisory
Exploit prediction
26.32% 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 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
securityfocus.com
/bid/8835
vdb-entry, patch, third-party-advisory, vendor-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2003/ms03-050
vendor-advisory
-
archives.neohapsis.com
/archives/bugtraq/2003-10/0163.html
mailing-list, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/13682
vdb-entry, third-party-advisory
-
security.nnov.ru
/search/document.asp?docid=5243
third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A336
vdb-entry, signature, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A668
vdb-entry, signature, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A586
vdb-entry, signature, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A585
vdb-entry, signature, third-party-advisory
Sources
- CVE List CVE-2003-0820
- NVD CVE-2003-0820
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.