{"answers":{"affected":"It affects 11 products.","exploited":"There is no known exploitation of CVE-2016-10305 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-10305 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-10305 is a critical vulnerability in n/a, published on 30 Mar 2017. 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-10305 and fix it if it is affected.\n\nWhat it is: CVE-2016-10305 is a critical vulnerability in n/a, published on 30 Mar 2017. 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-10305 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-2016-10305/ (Markdown: https://insights.sbomify.com/CVE-2016-10305/index.md)","id":"CVE-2016-10305","markdown":"https://insights.sbomify.com/CVE-2016-10305/index.md","name":"CVE-2016-10305","record":{"aliases":["GHSA-p6jx-jgrw-xrp7"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Trango wireless bridge","requires_auth":"none","summary":"Attackers can use a hidden root account with a default password to gain full control over Trango wireless bridge devices via SSH or Telnet.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"apex_firmware","vendor":"gotrango"},{"product":"apex_lynx_firmware","vendor":"gotrango"},{"product":"apex_orion_firmware","vendor":"gotrango"},{"product":"apex_plus_firmware","vendor":"gotrango"},{"product":"giga_firmware","vendor":"gotrango"},{"product":"giga_lynx_firmware","vendor":"gotrango"},{"product":"giga_orion_firmware","vendor":"gotrango"},{"product":"giga_plus_firmware","vendor":"gotrango"},{"product":"giga_pro_firmware","vendor":"gotrango"},{"product":"stratalink_firmware","vendor":"gotrango"},{"product":"stratalink_pro_firmware","vendor":"gotrango"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Trango Apex \u003c= 2.1.1, ApexLynx \u003c 2.0, ApexOrion \u003c 2.0, ApexPlus \u003c= 3.2.0, Giga \u003c= 2.6.1, GigaLynx \u003c 2.0, GigaOrion \u003c 2.0, GigaPlus \u003c= 3.2.3, GigaPro \u003c= 1.4.1, StrataLink \u003c 3.0, and StrataPro devices have a built-in, hidden root account, with a default password that was once stored in cleartext within a software update package on a Trango FTP server. This account is accessible via SSH and/or TELNET, and grants access to the underlying embedded UNIX OS on the device, allowing full control over it.","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 n/a","id":"CVE-2016-10305","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":"Hardcoded credentials in n/a","id":"CVE-2016-10306"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2016-10304"},"products":["n/a"],"published":"2017-03-30","related":[],"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":["n/a"]},"summary":"Attackers can use a hidden root account with a default password to gain full control over Trango wireless bridge devices via SSH or Telnet.","url":"https://insights.sbomify.com/CVE-2016-10305/"}