RuggedCom ROS Key Management Errors (Update A)
All information products included in http://ics-cert.us-cert.gov are provided "as is" for informational purposes only. The Department of Homeland Security (DHS) does not provide any warranties of any kind regarding any information contained within. DHS does not endorse any commercial product or service, referenced in this product or otherwise. Further dissemination of this product is governed by the Traffic Light Protocol (TLP) marking in the header. For more information about TLP, see http://www.us-cert.gov/tlp/.
ICS-CERT is aware of a public report of a hard-coded RSA SSL private key within the RuggedCom Rugged Operating System (ROS). The vulnerability with proof-of-concept (PoC) exploit code was publicly presented by security researcher Justin W. Clarke of Cylance Inc. According to this report, the vulnerability can be used to decrypt SSL traffic between an end user and a RuggedCom network device.
ICS-CERT notified the affected vendor of the report and asked the vendor to confirm the vulnerability and identify mitigations. ICS-CERT is issuing this alert to provide early notice of the report and identify baseline mitigations for reducing risks to these and other cybersecurity attacks.
The report included vulnerability details and PoC exploit code for the following vulnerability:
|Vulnerability Type||Remotely Exploitable||Impact|
|Key Management Errorsa||Yes||Loss of System Integrity|
--------- Begin Update A Part 1 of 3 --------
Further analysis by RuggedCom has identified similar vulnerabilities in the ROX (ROX I and ROX II) operating system firmware and the RuggedMax operating system firmware. A fix for the identified vulnerability in ROX is available. For the SSH service of RuggedMax, an interim mitigation for the identified vulnerability is also available.
Siemens has reported the following are affected products:
- Devices using the ROS releases before and including ROS Main v3.11.0.
- ROX I OS firmware used by RX1000 and RX1100 series products. ROX I versions before
- and including ROX v1.14.5 are affected.
- ROX II OS firmware used by RX5000 and RX1500 series products. ROX II versions before
- and including ROX v2.3.0 are affected.
- RuggedMax Operating System Firmware used by the Win7000 and Win7200 base station units and the Win5100 and Win5200 subscriber (CPE) devices. All versions of the firmware released before and including 126.96.36.19921.22.
--------- End Update A Part 1 of 3 ----------
Please report any issues affecting control systems in critical infrastructure environments to ICS-CERT.
Justin W. Clarke publicly reported that the RSA Private PKI key for SSL communication between a client/user and a RuggedCom switch can be identified in the ROS. An attacker may use the key to decrypt management traffic and create malicious communication to a RuggedCom network device.
--------- Begin Update A Part 2 of 3 --------
This vulnerability has no impact on encrypted data traffic passing through RuggedCom ROS, ROX, or RuggedMax BS devices.
--------- End Update A Part 2 of 3 ----------
ICS-CERT is currently coordinating with the vendor and security researcher to identify mitigations.
--------- Begin Update A Part 3 of 3 --------
Siemens has produced the following interim mitigations in Security Advisory SSA-622607:
RuggedCom is currently working to prepare a firmware update addressing the identified vulnerability in the ROS-based devices.
Until a fix for the related vulnerability is released, RuggedCom recommends that owners/operators take precautions to prevent attackers from intercepting traffic between administration systems and ROS devices. Customers may also contact RuggedCom’s Customer Support Team for assistance.
ROX device customers are strongly encouraged to change their SSL and SSH keys. RuggedCom application notes exist that explain how to change the SSL and SSH keys. Please consult App Note AN17 for ROX1.x versions of the firmware and App Note AN16 for ROX 2.x. These application notes can be obtained from RuggedCom’s Customer Support Team.
For RuggedMax SSH service, the customer has the capability to generate new keys. Each device (subscriber or base station) can be triggered to generate a new SSH key by deleting the current key. Customers are strongly encouraged to generate new keys. A procedure on how to generate a new SSH key can be obtained from RuggedCom Customer Support Team.
For the HTTPS access, a temporary solution exists with the current version of firmware to disable HTTPS access. For details on this procedure, please contact the RuggedCom Customer Support Team.
Siemens ProductCERT has also issued Security Advisory SSA-622607 to address these vulnerabilities.
--------- End Update A Part 3 of 3 ----------
ICS-CERT recommends that users take defensive measures to minimize the risk of exploitation of these vulnerabilities. Specifically, users should perform the following.
- Minimize network exposure for all control system devices. Control system devices should not directly face the Internet.b
- Locate control system networks and devices behind firewalls, and isolate them from the business network.
- If remote access is required, employ secure methods, such as Virtual Private Networks (VPNs), recognizing that VPN is only as secure as the connected devices.
ICS-CERT reminds organizations to perform proper impact analysis and risk assessment prior to taking defensive measures.
The Control Systems Security Program (CSSP) also provides a recommended practices section for control systems on the US-CERT Web site. Several recommended practices are available for reading or download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.
Organizations that observe any suspected malicious activity should follow their established internal procedures and report their findings to ICS-CERT for tracking and correlation against other incidents.
- a. MITRE, http://cwe.mitre.org/data/definitions/320.html, Web site last accessed August 31, 2012.
- b. ICS-CERT ALERT, http://ics-cert.us-cert.gov/alerts/ICS-ALERT-10-301-01, Web site last accessed August 31, 2012.
For any questions related to this report, please contact the NCCIC at:
Toll Free: 1-888-282-0870
The NCCIC continuously strives to improve its products and services. You can help by choosing one of the links below to provide feedback about this product.