# CVE-2014-1818: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted image file containing malicious EMF+ records.

- **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:** 11 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qgr4-fg4h-h77q

## What is CVE-2014-1818?

CVE-2014-1818 is a critical memory corruption vulnerability in Microsoft Windows 7, published on 11 Jun 2014. 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

GDI+ in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, Office 2007 SP3 and 2010 SP1 and SP2, Live Meeting 2007 Console, Lync 2010 and 2013, Lync 2010 Attendee, and Lync Basic 2013 allows remote attackers to execute arbitrary code via a crafted EMF+ record in an image file, aka "GDI+ Image Parsing Vulnerability."

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-1818?

It affects 9 products.


Products: Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Rt, Microsoft Windows Rt 8.1, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista.

## How do I fix CVE-2014-1818?

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

## Is CVE-2014-1818 being exploited?

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

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1818 and fix it if it is affected.

What it is: CVE-2014-1818 is a critical memory corruption vulnerability in Microsoft Windows 7, published on 11 Jun 2014. 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-2014-1818 in the wild and no public exploit code.

Affected product: Microsoft Windows 7. 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-2014-1818/ (Markdown: https://insights.sbomify.com/CVE-2014-1818/index.md)
```

## Sources

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

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