# CVE-2013-3906: Microsoft Graphics Component Memory Corruption

> Remote attackers can execute arbitrary code via crafted TIFF images in Microsoft Windows and Office applications.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Feb 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Nov 2013
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-7mhx-7529-p5jc

## What is CVE-2013-3906?

CVE-2013-3906 is a high-severity code injection vulnerability in Microsoft Excel Viewer, published on 6 Nov 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

GDI+ in Microsoft Windows Vista SP2 and Server 2008 SP2; Office 2003 SP3, 2007 SP3, and 2010 SP1 and SP2; Office Compatibility Pack SP3; and Lync 2010, 2010 Attendee, 2013, and Basic 2013 allows remote attackers to execute arbitrary code via a crafted TIFF image, as demonstrated by an image in a Word document, and exploited in the wild in October and November 2013.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2013-3906?

It affects 8 products.


Products: Microsoft Excel Viewer, Microsoft Lync, Microsoft Office, Microsoft Office Compatibility Pack, Microsoft Powerpoint Viewer, Microsoft Windows Server 2008, Microsoft Windows Vista, Microsoft Word Viewer.

## How do I fix CVE-2013-3906?

No fix has been published for CVE-2013-3906 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Aug 2022.

## Is CVE-2013-3906 being exploited?

Yes. Attackers have exploited CVE-2013-3906 in the wild since at least 15 Feb 2022.

Public exploit code:

- MS13-096 Microsoft Tagged Image File Format (TIFF) Integer Overflow (metasploit)
- Microsoft - Tagged Image File Format '.TIFF' Integer Overflow (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Excel Viewer

- [CVE-2019-0541](https://insights.sbomify.com/CVE-2019-0541/): Microsoft MSHTML Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-2424](https://insights.sbomify.com/CVE-2015-2424/): Microsoft PowerPoint Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2008-0113](https://insights.sbomify.com/CVE-2008-0113/): Memory corruption in n/a (critical 9.3)
- [CVE-2018-8432](https://insights.sbomify.com/CVE-2018-8432/): Memory corruption in Microsoft Excel Viewer (high 7.8)
- [CVE-2019-0540](https://insights.sbomify.com/CVE-2019-0540/): Security feature bypass in Microsoft Excel Viewer (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3906 and fix it if it is affected.

What it is: CVE-2013-3906 is a high-severity code injection vulnerability in Microsoft Excel Viewer, published on 6 Nov 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2013-3906 in the wild since at least 15 Feb 2022.

Affected product: Microsoft Excel Viewer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-3906/ (Markdown: https://insights.sbomify.com/CVE-2013-3906/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-3906
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-3906
- OSV: https://osv.dev/vulnerability/CVE-2013-3906

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-3906/
Summaries are generated and may contain mistakes; the official description above is the record.