dbcve.org
Office Filter PackApplication · Microsoft

CVE-2013-0079

HIGH · 9.3 CVSS v2.0 Published 2013-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft Visio Viewer 2010 SP1 allows remote attackers to execute arbitrary code via a crafted Visio file that triggers incorrect memory allocation, aka "Visio Viewer Tree Object Type Confusion Vulnerability."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Microsoft Visio Viewer 2010 SP1 contains a memory allocation vulnerability where parsing a specially crafted Visio file triggers incorrect memory handling, leading to a type confusion condition that can be exploited to achieve arbitrary code execution with high severity impact.

MitigationApply Microsoft security update KB2836352 or later to Visio Viewer 2010; alternatively, avoid opening untrusted Visio files and ensure users do not have local administrator privileges to limit exploitation impact.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Office Filter PackApplication
Affected:= 2010
VisioApplication
Affected:= 2010
Visio ViewerApplication
Affected:= 2010

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Visio Viewer 2010 installation
    Open PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Visio*Viewer*2010*'} | Select-Object DisplayName, DisplayVersion
    Affected if Visio Viewer 2010 is present and version is 2010 (no Service Pack or SP1 without KB2836352)
  2. Verify Visio 2010 installation
    Open PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Visio*2010*'} | Select-Object DisplayName, DisplayVersion
    Affected if Visio 2010 is present and version is 2010 without Service Pack or SP1 without KB2836352
  3. Verify Office Filter Pack 2010 installation
    Open PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Office*Filter*Pack*2010*'} | Select-Object DisplayName, DisplayVersion
    Affected if Office Filter Pack 2010 is present with version 2010
  4. Check for security update KB2836352
    Open PowerShell and run: Get-HotFix -Id KB2836352 -ErrorAction SilentlyContinue | Select-Object HotFixID, InstalledOn
    Affected if The hotfix KB2836352 is NOT installed on the system

A system is affected if any of Visio Viewer 2010, Visio 2010, or Office Filter Pack 2010 are installed without security update KB2836352 applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security update KB2836352 or later to Visio Viewer 2010; alternatively, avoid opening untrusted Visio files and ensure users do not have local administrator privileges to limit exploitation impact.

Recommended fix Moderate confidence

Microsoft Visio Viewer 2010 Service Pack 2 or later, or apply MS13-024 security update

  1. Open Windows Update or check Microsoft Update Catalog for available updates
  2. Search for security update related to MS13-024 or CVE-2013-0079
  3. Download and install the applicable security update for Microsoft Visio Viewer 2010
  4. Alternatively, download Microsoft Visio Viewer 2010 Service Pack 2 or later from official Microsoft download center
  5. Restart the system after applying the update
  6. Verify the update was successfully installed by checking installed updates
Caveat Standard Microsoft security update - minimal risk of breaking changes; ensure system meets prerequisites

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Office Filter Pack Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0079 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data