# CVE-2017-17692: Information disclosure in n/a

> Remote attackers can bypass Same Origin Policy to obtain sensitive information via crafted JavaScript in Samsung Internet Browser.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vp83-pfmp-prrm

## What is CVE-2017-17692?

CVE-2017-17692 is a high-severity vulnerability in n/a, published on 21 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Samsung Internet Browser 5.4.02.3 allows remote attackers to bypass the Same Origin Policy and obtain sensitive information via crafted JavaScript code that redirects to a child tab and rewrites the innerHTML property.

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

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

It affects 1 product.


Products: Samsung Internet Browser.

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

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

## Is CVE-2017-17692 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-17692 exists.

Public exploit code:

- Samsung Internet Browser SOP Bypass (metasploit)
- Samsung Internet Browser - SOP Bypass (Metasploit) (exploitdb)
- https://github.com/specloli/CVE-2017-17692 (github_poc): https://github.com/specloli/CVE-2017-17692

## Other vulnerabilities in n/a

- [CVE-2017-17859](https://insights.sbomify.com/CVE-2017-17859/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17692 is a high-severity vulnerability in n/a, published on 21 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-17692 exists.

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

## Sources

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

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