# CVE-2017-10890: Auth bypass in RX-CLV1-P firmware

> An attacker on the same network can hijack sessions to perform arbitrary operations or access information on Sharp AV receivers.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:A/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 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rw9g-3c7m-wwc6

## What is CVE-2017-10890?

CVE-2017-10890 is a medium-severity authentication bypass vulnerability in Sharp Corporation RX-CLV1-P firmware, published on 17 Nov 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

Session management issue in RX-V200 firmware versions prior to 09.87.17.09, RX-V100 firmware versions prior to 03.29.17.09, RX-CLV1-P firmware versions prior to 79.17.17.09, RX-CLV2-B firmware versions prior to 89.07.17.09, RX-CLV3-N firmware versions prior to 91.09.17.10 allows an attacker on the same LAN to perform arbitrary operations or access information via unspecified vectors.

Weakness: CWE-384 (Session Fixation)

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

It affects 5 products.


Products: Sharp Rx-Clv1-P Firmware, Sharp Rx-Clv2-B Firmware, Sharp Rx-Clv3-N Firmware, Sharp Rx-V100 Firmware, Sharp Rx-V200 Firmware.

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

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

## Is CVE-2017-10890 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10890 is a medium-severity authentication bypass vulnerability in Sharp Corporation RX-CLV1-P firmware, published on 17 Nov 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-10890 in the wild and no public exploit code.

Affected product: Sharp Corporation RX-CLV1-P firmware. 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-10890/ (Markdown: https://insights.sbomify.com/CVE-2017-10890/index.md)
```

## Sources

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

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