CVE-2016-9497
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHughes high-performance broadband satellite modems, models HN7740S DW7000 HN7000S/SM, is vulnerable to an authentication bypass using an alternate path or channel. By default, port 1953 is accessible via telnet and does not require authentication. An unauthenticated remote user can access many administrative commands via this interface, including rebooting the modem.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHughes high-performance broadband satellite modems (HN7740S, DW7000, HN7000S/SM) contain an authentication bypass vulnerability where port 1953 is accessible via telnet without requiring any credentials. This allows unauthenticated remote attackers to access administrative commands including device reboot capabilities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.9.0.34= 6.9.0.34= 6.9.0.34= 6.9.0.34CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Hughes modem modelCheck the device label, web interface, or SNMP inventory for model number HN7740S, DW7000, HN7000S, or HN7000SMAffected if Device is not one of these four models - not affected
-
Check firmware versionAccess device web interface, use SNMP, or query the device via telnet/SSH to retrieve firmware version. The affected version is exactly 6.9.0.34Affected if Firmware version is not 6.9.0.34 - not affected (only exact version listed is vulnerable)
-
Verify telnet port 1953 is openRun 'telnet <device_ip> 1953' or use 'nmap -p 1953 <device_ip>' to check if the telnet service is accessible on port 1953Affected if Port 1953 is closed or filtered - not affected
-
Test unauthenticated telnet accessConnect via telnet to port 1953 without providing any credentials. Attempt to access administrative commands such as reboot optionsAffected if Telnet on port 1953 accepts connection without authentication and allows administrative commands - VULNERABLE
Affected only if the device is a Hughes HN7740S, DW7000, HN7000S, or HN7000SM with firmware version 6.9.0.34 AND telnet port 1953 is accessible without credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict or disable telnet access on port 1953 through firewall rules, network segmentation, or disabling the telnet service entirely on the affected devices. Apply vendor patches if available.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9497 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-9497 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data