CVE-2012-0137: n/a vulnerability

CVE-2012-0137: Microsoft Visio Viewer 2010 Gold and SP1 does not properly handle memory during the parsing of files, which...

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-0138.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 18:16 UTC (UTC+00:00)

Security readout for executives and security teams

This is a legacy Microsoft Visio Viewer 2010 flaw. A malicious Visio file could trigger memory corruption and let an attacker run code on a user’s machine. Business risk is highest where old Visio Viewer installations remain and users can receive or open untrusted Visio files. Exposure is likely limited to environments still running Microsoft Visio Viewer 2010 Gold or SP1, especially endpoints handling externally supplied Visio files. Modern estates without this legacy viewer are less likely exposed, but asset inventory is needed because the provided affected-product metadata is incomplete. Prioritize remediation if legacy Visio Viewer 2010 exists in the environment. The issue enables code execution, but urgency is lower for organizations that have removed this viewer or block untrusted Visio files. No active exploitation evidence is provided in the source bundle. Mitigation focus: Apply the Microsoft security update guidance associated with MS12-015.; Remove unsupported or unnecessary Visio Viewer 2010 installations.; Restrict handling of untrusted Visio files on legacy endpoints..

Prepared: Jun 27, 2026, 17:28 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2012-0137 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Feb 14, 2012, 22:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
oval:org.mitre.oval:def:14602CVE reference · vdb-entry, signature
MS12-015CVE reference · vendor-advisory, x_refsource_MS

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.