# CVE-2017-11919: Information disclosure in ChakraCore, Internet Explorer, Microsoft Edge

> An attacker can obtain sensitive information to further compromise the user's system via a scripting engine memory handling flaw in Microsoft browsers.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 12 Dec 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-r7cg-pp63-f4xg

## What is CVE-2017-11919?

CVE-2017-11919 is a medium-severity vulnerability in Microsoft Chakracore, published on 12 Dec 2017. 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

ChakraCore, and Internet Explorer in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 R2, and Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016, and Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to obtain information to further compromise the user's system, due to how the scripting engine handles objects in memory, aka "Scripting Engine Information Disclosure Vulnerability". This CVE ID is unique from CVE-2017-11887 and CVE-2017-11906.

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

## Which versions are affected by CVE-2017-11919?

It affects 3 products.


Products: Microsoft Chakracore, Microsoft Edge, Microsoft Internet Explorer.

## How do I fix CVE-2017-11919?

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

## Is CVE-2017-11919 being exploited?

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

## Other vulnerabilities in Microsoft Chakracore

- [CVE-2018-8298](https://insights.sbomify.com/CVE-2018-8298/): ChakraCore Scripting Engine Type Confusion (high 7.5, exploited in the wild)
- [CVE-2020-0878](https://insights.sbomify.com/CVE-2020-0878/): Microsoft Edge and Internet Explorer Memory Corruption (medium 4.2, exploited in the wild)
- [CVE-2018-8500](https://insights.sbomify.com/CVE-2018-8500/): ChakraCore RCE Vulnerability (critical 9.8)
- [CVE-2017-11767](https://insights.sbomify.com/CVE-2017-11767/): ChakraCore vulnerable to privilege escalation (critical 9.8)
- [CVE-2017-8658](https://insights.sbomify.com/CVE-2017-8658/): ChakraCore RCE Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11919 and fix it if it is affected.

What it is: CVE-2017-11919 is a medium-severity vulnerability in Microsoft Chakracore, published on 12 Dec 2017. 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-2017-11919 in the wild and no public exploit code.

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

## Sources

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

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