# CVE-2019-1030: Microsoft Edge based on Edge HTML Information Disclosure Vulnerability

> An attacker can trick a user into visiting a malicious site to leak memory information, potentially aiding further system compromise.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:P/RL:O/RC: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:** 14 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-78p9-q5qg-rg87

## What is CVE-2019-1030?

CVE-2019-1030 is a medium-severity vulnerability in Microsoft Edge, published on 14 Aug 2019. 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

An information disclosure vulnerability exists when Microsoft Edge based on Edge HTML improperly handles objects in memory. An attacker who successfully exploited the vulnerability could obtain information to further compromise the user’s system.
To exploit the vulnerability, in a web-based attack scenario, an attacker could host a website in an attempt to exploit the vulnerability. In addition, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could exploit the vulnerability. However, in all cases an attacker would have no way to force a user to view the attacker-controlled content. Instead, an attacker would have to convince a user to take action. For example, an attacker could trick a user into clicking a link that takes the user to the attacker's site.
The update addresses the vulnerability by modifying how Microsoft Edge based on Edge HTML handles objects in memory.

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

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

It affects 1 product.


Products: Microsoft Edge.

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

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

## Is CVE-2019-1030 being exploited?

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

## Other vulnerabilities in Microsoft Edge

- [CVE-2021-26411](https://insights.sbomify.com/CVE-2021-26411/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7200](https://insights.sbomify.com/CVE-2016-7200/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7201](https://insights.sbomify.com/CVE-2016-7201/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2017-0037](https://insights.sbomify.com/CVE-2017-0037/): Microsoft Edge and Internet Explorer Type Confusion (high 8.1, exploited in the wild)
- [CVE-2016-3351](https://insights.sbomify.com/CVE-2016-3351/): Microsoft Internet Explorer and Edge Information Disclosure (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1030 is a medium-severity vulnerability in Microsoft Edge, published on 14 Aug 2019. 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-2019-1030 in the wild and no public exploit code.

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

## Sources

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

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