# CVE-2019-1148: Microsoft Graphics Component Information Disclosure Vulnerability

> An attacker with local access can exploit a memory handling flaw in the Windows Graphics Component to disclose sensitive information.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wfpv-3m23-c38r

## What is CVE-2019-1148?

CVE-2019-1148 is a medium-severity vulnerability in Microsoft Office, published on 14 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An information disclosure vulnerability exists when the Microsoft Windows Graphics Component improperly handles objects in memory. An attacker who successfully exploited the vulnerability could obtain information to further compromise the user’s system.
To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application.
The update addresses the vulnerability by correcting the way in which the Windows Graphics Component handles objects in memory.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-1148?

It affects 9 products.


Products: Microsoft Office, Microsoft Windows 10, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019.

## How do I fix CVE-2019-1148?

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

## Is CVE-2019-1148 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1148 exists.

Public exploit code:

- Microsoft Font Subsetting - DLL Heap-Based Out-of-Bounds read in GetGlyphIdx (exploitdb)

## Other vulnerabilities in Microsoft Office

- [CVE-2018-0798](https://insights.sbomify.com/CVE-2018-0798/): Microsoft Office Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild)
- [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild)
- [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1148 and fix it if it is affected.

What it is: CVE-2019-1148 is a medium-severity vulnerability in Microsoft Office, published on 14 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1148 exists.

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

## Sources

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

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