# CVE-2012-2897: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted TrueType font files due to improper memory handling in Windows kernel-mode drivers.

- **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:** Not known
- **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:** 26 Sep 2012
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-9wvr-xp2q-8fqg

## What is CVE-2012-2897?

CVE-2012-2897 is a high-severity memory corruption vulnerability in Google Chrome, published on 26 Sep 2012. 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

The kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, Windows 7 Gold and SP1, Windows 8, Windows Server 2012, and Windows RT, as used by Google Chrome before 22.0.1229.79 and other programs, do not properly handle objects in memory, which allows remote attackers to execute arbitrary code via a crafted TrueType font file, aka "Windows Font Parsing Vulnerability" or "TrueType Font Parsing Vulnerability."

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

## Which versions are affected by CVE-2012-2897?

It affects 9 products.


Products: Google Chrome, Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows Rt, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2012-2897?

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

## Is CVE-2012-2897 being exploited?

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

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2897 and fix it if it is affected.

What it is: CVE-2012-2897 is a high-severity memory corruption vulnerability in Google Chrome, published on 26 Sep 2012. 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: There is no known exploitation of CVE-2012-2897 in the wild and no public exploit code.

Affected product: Google Chrome. 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-2012-2897/ (Markdown: https://insights.sbomify.com/CVE-2012-2897/index.md)
```

## Sources

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

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