CVE-2012-0138: Code Injection
First published: Tue Feb 14 2012(Updated: )
Microsoft Visio Viewer 2010 Gold and SP1 does not properly handle memory during the parsing of files, which allows remote attackers to execute arbitrary code via crafted attributes in a Visio file, aka "VSD File Format Memory Corruption Vulnerability," a different vulnerability than CVE-2012-0019, CVE-2012-0020, CVE-2012-0136, and CVE-2012-0137.
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft Visio Viewer 2016 | =2010 | |
| Microsoft Visio Viewer 2016 | =2010-sp1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2012-0138?
CVE-2012-0138 has a critical severity rating due to its potential to allow remote code execution.
How do I fix CVE-2012-0138?
To mitigate CVE-2012-0138, install the necessary security updates provided by Microsoft for Visio Viewer 2010.
Who is affected by CVE-2012-0138?
CVE-2012-0138 affects users of Microsoft Visio Viewer 2010 and Microsoft Visio Viewer 2010 SP1.
What types of attacks can exploit CVE-2012-0138?
CVE-2012-0138 can be exploited through specially crafted Visio files that trigger memory corruption.
Is there a patch available for CVE-2012-0138?
Yes, Microsoft has released security updates to address CVE-2012-0138.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/weakness
- agent/severity
- agent/references
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/microsoft
- canonical/microsoft visio viewer 2016
- version/microsoft visio viewer 2016/2010
- version/microsoft visio viewer 2016/2010-sp1