CVE-2017-10890 json
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 firmw…
published 8y ago modified 4mo ago also EUVD-2017-2530
- cvss
- 4.6
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- sharp rx-v200_firmware 09.87.17.09
- sharp rx-v100_firmware 03.29.17.09
- sharp rx-clv1-p_firmware 79.17.17.09
- sharp rx-clv2-b_firmware 89.07.17.09
- sharp rx-clv3-n_firmware 91.09.17.10
Is CVE-2017-10890 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.6 | CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:A/AC:M/Au:N/C:P/I:P/A:N |
Affected products
- Sharp Corporation RX-V200 firmware
- Sharp Corporation RX-V100 firmware
- Sharp Corporation RX-CLV1-P firmware
- Sharp Corporation RX-CLV2-B firmware
- Sharp Corporation RX-CLV3-N firmware
Classification
- Weakness
-
- CWE-384 Session Fixation
References
-
jvn.jp
/en/jp/JVN76382932/index.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2017-10890
- NVD CVE-2017-10890
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.