{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-13718 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-13718 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-13718 is a high-severity authentication bypass vulnerability in n/a, published on 10 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-13718 and fix it if it is affected.\n\nWhat it is: CVE-2017-13718 is a high-severity authentication bypass vulnerability in n/a, published on 10 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-13718 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-13718/ (Markdown: https://insights.sbomify.com/CVE-2017-13718/index.md)","id":"CVE-2017-13718","markdown":"https://insights.sbomify.com/CVE-2017-13718/index.md","name":"CVE-2017-13718","record":{"aliases":["GHSA-cpcg-x4f2-x9fr"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Starry Router","requires_auth":"low_privilege","summary":"Attackers can brute force the router PIN via HTTP API to change Wi-Fi settings, port forward, and steal sensitive device information.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"s00111_firmware","vendor":"starry"}],"cvss":{"score":8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-254","name":null}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2017-13718","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-13719"},"packages":[],"prev":{"headline":"Misconfiguration in n/a","id":"CVE-2017-13717"},"products":["n/a"],"published":"2019-06-10","related":[{"cvss_score":8.8,"headline":"Misconfiguration in n/a","id":"CVE-2017-13717","kev_date_added":null,"published":"2019-06-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can brute force the router PIN via HTTP API to change Wi-Fi settings, port forward, and steal sensitive device information.","url":"https://insights.sbomify.com/CVE-2017-13718/"}