Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2016-10307: Trango ApexLynx 2.0, ApexOrion 2.0, GigaLynx 2.0, GigaOrion 2.0, and StrataLink 3.0 devices have a built-in, h

65
This week
CRITICAL 9.8REMOTEMITIGATEMITIGATEMITIGATE

CVE-2016-10307 is a critical-severity flaw (CVSS 9.8) affecting apex lynx firmware, apex orion firmware, giga lynx firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Trango ApexLynx 2.0, ApexOrion 2.0, GigaLynx 2.0, GigaOrion 2.0, and StrataLink 3.0 devices have a built-in, hidden root account, with a default password for which the MD5 hash value is public (but the cleartext value is perhaps not yet public). 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.

Why this priority

  • Critical severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.4% (top 16%)
CISA exploited listNo
WeaknessCWE-798
Published2017-03-30
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: gotrango

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

gotrango apex lynx firmware MITIGATE
Affected: 2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
gotrango apex orion firmware MITIGATE
Affected: 2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
gotrango giga lynx firmware MITIGATE
Affected: 2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
gotrango giga orion firmware MITIGATE
Affected: 2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
gotrango stratalink firmware UPGRADE
Affected: <= 3.0
Fixed in: newer than 3.0
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-10307?

apex lynx firmware: mitigate or apply the listed mitigation; apex orion firmware: mitigate or apply the listed mitigation; giga lynx firmware: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-10307 being exploited?

CVE-2016-10307 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-10307 affect?

CVE-2016-10307 affects apex lynx firmware, apex orion firmware, giga lynx firmware. Severity is critical (CVSS 9.8). Trango ApexLynx 2.0, ApexOrion 2.0, GigaLynx 2.0, GigaOrion 2.0, and StrataLink 3.0 devices have a built-in, hidden root account, with a default password for which the MD5 hash value is public (but the cleartext value is perhaps not yet pub

How urgent is CVE-2016-10307?

Priority 65/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.