Every CVESearch/Get API key

CVE-2009-0097

Microsoft Office Visio 2002 SP2 and 2003 SP3 does not properly validate memory allocation for...

9.3 High

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.

What does this mean?
Severity
9.3 HighCVSS 2.0, NVD
Exploit chance
22.6%EPSS, 97th percentile
Exploitation
None knownNot on CISA’s or ENISA’s lists
Fixed in
No fix listedNo source names one

Description

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

22.6%Down 22.5 points since Feb 4, 2022
90%50%10%1%

Affected products

What each source reports

NVD Score used9.3

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 HighAV:N/AC:M/Au:N/C:C/I:C/A:C
Weakness
CWE-399
Updated
2026-11-02
CVE ListNo 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-0106No 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-f9r3No 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

History

History
RecordedChangedSources
facts
aliasesEUVD
first indexedCVE List, GitHub Advisories, NVD

Dates are when Every CVE recorded each change. Upstream dates may differ.

References

MoveEnter Open