# CVE-2017-10963: Other in n/a

> A man-in-the-middle attacker can inject malicious applications into the Samsung Knox container, enabling unauthorized code execution and data leakage.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/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:** 20 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h3pf-mvgp-g8g3

## What is CVE-2017-10963?

CVE-2017-10963 is a medium-severity vulnerability in n/a, published on 20 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Knox SDS IAM (Identity Access Management) and EMM (Enterprise Mobility Management) 16.11 on Samsung mobile devices, a man-in-the-middle attacker can install any application into the Knox container (without the user's knowledge) by inspecting network traffic from a Samsung server and injecting content at a certain point in the update sequence. This installed application can further leak information stored inside the Knox container to the outside world.

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

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

It affects 2 products.


Products: Samsung Knox Enterprise Mobility Management, Samsung Knox Identity Access Management.

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

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

## Is CVE-2017-10963 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10963 is a medium-severity vulnerability in n/a, published on 20 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10963 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-10963/ (Markdown: https://insights.sbomify.com/CVE-2017-10963/index.md)
```

## Sources

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

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