CVE-2017-13718
HIGHEPSS 80th pctlDescription
The HTTP API supported by Starry Station (aka Starry Router) allows brute forcing the PIN setup by the user on the device, and this allows an attacker to change the Wi-Fi settings and PIN, as well as port forward and expose any internal device's port to the Internet. It was identified that the device uses custom Python code called "rodman" that allows the mobile appication to interact with the device. The APIs that are a part of this rodman Python file allow the mobile application to interact with the device using a secret, which is a uuid4 based session identifier generated by the device the first time it is set up. However, in some cases, these APIs can also use a security code. This security code is nothing but the PIN number set by the user to interact with the device when using the touch interface on the router. This allows an attacker on the Internet to interact with the router's HTTP interface when a user navigates to the attacker's website, and brute force the credentials. Also, since the device's server sets the Access-Control-Allow-Origin header to "*", an attacker can easily interact with the JSON payload returned by the device and steal sensitive information about the device.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Exploit Intelligence
Elevated risk: more likely to be exploited than 80% of all known CVEs.
References
Related Vulnerabilities
Other CWE-254 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2016-0161 | Medium | 6.5 | 69% | - | - |
| CVE-2016-2296 | Critical | 9.4 | 64% | - | - |
| CVE-2015-1793 | Medium | 6.5 | 62% | - | Fix |
| CVE-2016-2118 | High | 7.5 | 37% | - | Fix |
| CVE-2016-3238 | High | 8.1 | 35% | - | - |
| CVE-2016-3198 | Medium | 6.5 | 32% | - | - |
Common questions
How do I fix CVE-2017-13718?
No published fix for CVE-2017-13718 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2017-13718 being actively exploited?
Not that we know of. CVE-2017-13718 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 2.1% is the estimated probability that it will be exploited in the next 30 days. That is higher than 80% of all scored CVEs.
How severe is CVE-2017-13718?
CVE-2017-13718 has a CVSS v3 base score of 8.0, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2017-13718
Markdown
[](https://tridentstack.com/cve/CVE-2017-13718)HTML
<a href="https://tridentstack.com/cve/CVE-2017-13718"><img src="https://tridentstack.com/cve/badge/CVE-2017-13718.svg" alt="CVE-2017-13718"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.