dbcve.org
Sixnet Managed Industrial Switches FirmwareOperating system · Redlion

CVE-2016-9335

CRITICAL · 10.0 CVSS v3.0 Published 2018-05-09
Fix available
A fix is available. Upgrade to after 5.0.196 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A hard-coded cryptographic key vulnerability was identified in Red Lion Controls Sixnet-Managed Industrial Switches running firmware Version 5.0.196 and Stride-Managed Ethernet Switches running firmware Version 5.0.190. Vulnerable versions of Stride-Managed Ethernet switches and Sixnet-Managed Industrial switches use hard-coded HTTP SSL/SSH keys for secure communication. Because these keys cannot be regenerated by users, all products use the same key. The attacker could disrupt communication or compromise the system. CVSS v3 base score: 10, CVSS vector string: (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Red Lion Controls recommends updating to SLX firmware Version 5.3.174.

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 · moderate confidence

Hard-coded cryptographic SSL/SSH keys in firmware versions 5.0.196 (Sixnet-Managed) and 5.0.190 (Stride-Managed) cannot be regenerated by users, meaning all devices share identical keys. Attackers with the key can decrypt communications or compromise any affected device.

MitigationUpdate to SLX firmware Version 5.3.174 which either removes hard-coded keys or enables key regeneration.

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
Sixnet Managed Industrial Switches FirmwareOperating system
Affected:<= 5.0.196
Stride Managed Ethernet Switches FirmwareOperating system
Affected:<= 5.0.190

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Log into the switch CLI or web interface and run 'show version' or check the device info page to confirm it is a Red Lion Sixnet Managed Industrial Switch or Red Lion Stride Managed Ethernet Switch
    Affected if Device is a Sixnet-Managed or Stride-Managed switch from Red Lion
  2. Check installed firmware version
    Run 'show version' or access the firmware/version information in the web interface to retrieve the current firmware version
    Affected if Firmware version is 5.0.196 or lower for Sixnet-Managed, or 5.0.190 or lower for Stride-Managed
  3. Confirm SSL/SSH access is enabled
    Check the switch configuration for SSL web interface or SSH access settings, typically via 'show running-config' or in the web management under Services or Security settings
    Affected if SSL (HTTPS) web interface or SSH access is enabled on the device
  4. Verify if SSH or HTTPS is accessible from network
    Attempt to connect to the device on port 443 (HTTPS) or port 22 (SSH) from an external system, or review access control lists
    Affected if HTTPS or SSH service is reachable from the network where an attacker could use the hardcoded keys

You are affected if you have a Red Lion Sixnet or Stride managed switch running firmware at or below the affected version with SSL or SSH services enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 5.0.196
Interim mitigation

Update to SLX firmware Version 5.3.174 which either removes hard-coded keys or enables key regeneration.

Recommended fix High confidence

SLX firmware Version 5.3.174

  1. 1. Identify the specific device model (Sixnet Managed Industrial Switch or Stride Managed Ethernet Switch)
  2. 2. Check the current firmware version on the device
  3. 3. Download SLX firmware Version 5.3.174 from the official Red Lion Controls support website or authorized distribution channel
  4. 4. Review the device's firmware upgrade documentation for any specific prerequisites
  5. 5. Follow the vendor's standard firmware update procedure to apply Version 5.3.174 to the affected device
  6. 6. After upgrade, verify the new firmware version is installed and the device operates normally

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sixnet Managed Industrial Switches Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-9335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-9335 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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