{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-8717 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-8717 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-8717 is a critical vulnerability in Talos Moxa, published on 2 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-8717 and fix it if it is affected.\n\nWhat it is: CVE-2016-8717 is a critical vulnerability in Talos Moxa, published on 2 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-8717 in the wild and no public exploit code.\n\nAffected product: Talos Moxa. 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-2016-8717/ (Markdown: https://insights.sbomify.com/CVE-2016-8717/index.md)","id":"CVE-2016-8717","markdown":"https://insights.sbomify.com/CVE-2016-8717/index.md","name":"CVE-2016-8717","record":{"aliases":["GHSA-244f-3h24-62fj"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Wireless Access Point","requires_auth":"none","summary":"Attackers can gain full root control of Moxa AWK-3131A devices by exploiting hard-coded credentials in the firmware.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"awk-3131a_firmware","vendor":"moxa"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An exploitable Use of Hard-coded Credentials vulnerability exists in the Moxa AWK-3131A Wireless Access Point running firmware 1.1. The device operating system contains an undocumented, privileged (root) account with hard-coded credentials, giving attackers full control of affected devices.","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":"Hardcoded credentials in Moxa","id":"CVE-2016-8717","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in AWK-3131A Series Industrial IEEE 802.11a/b/g/n wireless AP/bridge/client","id":"CVE-2016-8718"},"packages":[],"prev":{"headline":"Information disclosure in AWK-3131A Series Industrial IEEE 802.11a/b/g/n wireless AP/bridge/client","id":"CVE-2016-8716"},"products":["Moxa"],"published":"2018-04-02","related":[{"cvss_score":10,"headline":"Command injection in Moxa","id":"CVE-2017-14459","kev_date_added":null,"published":"2018-04-11"},{"cvss_score":9.9,"headline":"Command injection in Moxa","id":"CVE-2019-5138","kev_date_added":null,"published":"2020-02-25"},{"cvss_score":9.9,"headline":"Memory corruption in Moxa","id":"CVE-2019-5153","kev_date_added":null,"published":"2020-02-25"},{"cvss_score":9.9,"headline":"Missing authorization in Moxa","id":"CVE-2019-5162","kev_date_added":null,"published":"2020-02-25"},{"cvss_score":9.1,"headline":"Command injection in Moxa AWK-3131A WAP","id":"CVE-2016-8721","kev_date_added":null,"published":"2017-04-20"},{"cvss_score":8.8,"headline":"Privilege escalation in Moxa","id":"CVE-2019-5136","kev_date_added":null,"published":"2020-02-25"}],"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-09-16","vendors":["Talos"]},"summary":"Attackers can gain full root control of Moxa AWK-3131A devices by exploiting hard-coded credentials in the firmware.","url":"https://insights.sbomify.com/CVE-2016-8717/"}