# CVE-2017-0154: Security feature bypass in Internet Explorer

> Attackers can bypass cross-domain policies in Internet Explorer to access and inject information across domains, leading to privilege escalation.

- **Severity:** Medium 4.4 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3cfq-pxwf-wqwq

## What is CVE-2017-0154?

CVE-2017-0154 is a medium-severity vulnerability in Microsoft Internet Explorer, published on 17 Mar 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Microsoft Internet Explorer 11 on Windows 10, 1511, and 1606 and Windows Server 2016 does not enforce cross-domain policies, allowing attackers to access information from one domain and inject it into another via a crafted application, aka, "Internet Explorer Elevation of Privilege Vulnerability."

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Microsoft Internet Explorer.

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

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

## Is CVE-2017-0154 being exploited?

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

## Other vulnerabilities in Microsoft Internet Explorer

- [CVE-2014-1776](https://insights.sbomify.com/CVE-2014-1776/): Microsoft Internet Explorer Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2021-27085](https://insights.sbomify.com/CVE-2021-27085/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0222](https://insights.sbomify.com/CVE-2017-0222/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0210](https://insights.sbomify.com/CVE-2017-0210/): Microsoft Internet Explorer Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2017-0149](https://insights.sbomify.com/CVE-2017-0149/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-0154 is a medium-severity vulnerability in Microsoft Internet Explorer, published on 17 Mar 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-0154 in the wild and no public exploit code.

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

## Sources

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

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