# CVE-2008-3012: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a malformed EMF image file processed by the GDI+ library.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-274p-j7q8-fx9w

## What is CVE-2008-3012?

CVE-2008-3012 is a critical memory corruption vulnerability in Microsoft Internet Explorer, published on 10 Sep 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

gdiplus.dll in GDI+ in Microsoft Internet Explorer 6 SP1, Windows XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, Server 2008, Office XP SP3, Office 2003 SP2 and SP3, 2007 Microsoft Office System Gold and SP1, Visio 2002 SP2, PowerPoint Viewer 2003, Works 8, Digital Image Suite 2006, SQL Server 2000 Reporting Services SP2, SQL Server 2005 SP2, Report Viewer 2005 SP1 and 2008, and Forefront Client Security 1.0 does not properly perform memory allocation, which allows remote attackers to execute arbitrary code via a malformed EMF image file, aka "GDI+ EMF Memory Corruption Vulnerability."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-3012?

It affects 16 products.


Products: Microsoft Digital Image Suite, Microsoft Forefront Client Security, Microsoft Internet Explorer, Microsoft Office, Microsoft Office Powerpoint Viewer, Microsoft Office System, Microsoft Report Viewer, Microsoft Server, Microsoft Sql Server, Microsoft Sql Server Reporting Services, Microsoft Visio, Microsoft Windows, Microsoft Windows-Nt, Microsoft Windows Vista, Microsoft Windows Xp, Microsoft Works.

## How do I fix CVE-2008-3012?

No fix has been published for CVE-2008-3012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-3012 being exploited?

There is no known exploitation of CVE-2008-3012 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Internet Explorer

- [CVE-2007-5348](https://insights.sbomify.com/CVE-2007-5348/): Integer overflow in n/a (critical 9.3)
- [CVE-2008-3013](https://insights.sbomify.com/CVE-2008-3013/): Memory corruption in n/a (critical 9.3)
- [CVE-2008-3014](https://insights.sbomify.com/CVE-2008-3014/): Memory corruption in n/a (critical 9.3)
- [CVE-2008-3015](https://insights.sbomify.com/CVE-2008-3015/): Integer overflow in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3012 and fix it if it is affected.

What it is: CVE-2008-3012 is a critical memory corruption vulnerability in Microsoft Internet Explorer, published on 10 Sep 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-3012 in the wild and no public exploit code.

Affected product: Microsoft Internet Explorer. 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-2008-3012/ (Markdown: https://insights.sbomify.com/CVE-2008-3012/index.md)
```

## Sources

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

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