# CVE-2017-17859: Cross-site scripting in n/a

> Remote attackers can bypass Same Origin Policy and execute scripts via MHTML files to steal sensitive information in Samsung Internet Browser.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 24 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9287-x9jc-rx96

## What is CVE-2017-17859?

CVE-2017-17859 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 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

Samsung Internet Browser 6.2.01.12 allows remote attackers to bypass the Same Origin Policy, and conduct UXSS attacks to obtain sensitive information, via vectors involving an IFRAME element inside XSLT data in one part of an MHTML file. Specifically, JavaScript code in another part of this MHTML file does not have a document.domain value corresponding to the domain that is hosting the MHTML file, but instead has a document.domain value corresponding to an arbitrary URL within the content of the MHTML file.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Samsung Internet Browser.

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

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

## Is CVE-2017-17859 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17692](https://insights.sbomify.com/CVE-2017-17692/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17859 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 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-17859 in the wild and no public exploit code.

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

## Sources

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

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