CVE-2009-0097
Microsoft Office Visio 2002 SP2 and 2003 SP3 does not properly validate memory allocation for...
Microsoft Office Visio 2002 SP2 and 2003 SP3 does not properly validate memory allocation for Visio files, which allows remote attackers to execute arbitrary code via a crafted file, aka "Memory Corruption Vulnerability."
Exploit likelihood
What each source reports
NVD Score used
Microsoft Office Visio 2002 SP2 and 2003 SP3 does not properly validate memory allocation for Visio files, which allows remote attackers to execute arbitrary code via a crafted file, aka "Memory Corruption Vulnerability."
- Record
CVE-2009-0097- CVSS 2.0
- 9.3 High
AV:N/AC:M/Au:N/C:C/I:C/A:C - Weakness
- CWE-399
- Updated
- 2026-11-02
CVE List No score
Microsoft Office Visio 2002 SP2 and 2003 SP3 does not properly validate memory allocation for Visio files, which allows remote attackers to execute arbitrary code via a crafted file, aka "Memory Corruption Vulnerability."
- Record
CVE-2009-0097- Updated
- 2026-11-02
EUVDEUVD-2009-0106 No score
Microsoft Office Visio 2002 SP2 and 2003 SP3 does not properly validate memory allocation for Visio files, which allows remote attackers to execute arbitrary code via a crafted file, aka "Memory Corruption Vulnerability."
- Record
EUVD-2009-0106- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-3jqr-q83p-f9r3 No score
Microsoft Office Visio 2002 SP2 and 2003 SP3 does not properly validate memory allocation for...
Microsoft Office Visio 2002 SP2 and 2003 SP3 does not properly validate memory allocation for Visio files, which allows remote attackers to execute arbitrary code via a crafted file, aka "Memory Corruption Vulnerability."
- Record
GHSA-3jqr-q83p-f9r3- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2009-0097 is a high vulnerability (CVSS 9.3) in Microsoft Visio, published February 10, 2009. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 22.6%, the 97th percentile. No source names a fixed version.
References
vupen.com/english/advisories/2009/0391
docs.microsoft.com/en-us/security-updates/securitybulletins/2009/ms09-005
oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6188
us-cert.gov/cas/techalerts/TA09-041A.html
nvd.nist.gov/vuln/detail/CVE-2009-0097
github.com/advisories/GHSA-3jqr-q83p-f9r3