# CVE-2019-1402: Information disclosure in Microsoft Office

> Attackers can exploit improper memory handling in Microsoft Office 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`)
- **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:** 12 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-59hc-rfcg-f7w2

## What is CVE-2019-1402?

CVE-2019-1402 is a medium-severity vulnerability in Microsoft Office, published on 12 Nov 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 in Microsoft Office software when the software fails to properly handle objects in memory, aka 'Microsoft Office Information Disclosure Vulnerability'.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Microsoft Office, Microsoft Office 365.

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

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

## Is CVE-2019-1402 being exploited?

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

Public exploit code:

- The latest workaround for the "Query is corrupt" error introduced with CVE-2019-1402 (github_poc): https://github.com/lauxjpn/CorruptQueryAccessWorkaround

## 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-1402 and fix it if it is affected.

What it is: CVE-2019-1402 is a medium-severity vulnerability in Microsoft Office, published on 12 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1402 in the wild and no public exploit code.

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-1402/ (Markdown: https://insights.sbomify.com/CVE-2019-1402/index.md)
```

## Sources

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

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