Bar Ofner
Twenty-plus years of connecting everything in our lives to the internet has brought us to a place where our ability to innovate and sustain our existence relies in some way on computer code.
Meanwhile, the emergence and prevalence of these cyber physical systems that have a direct touchpoint to the physical world is forcing a new paradigm of risk management decisions.
That’s the context under which we have revamped our biannual report. The State of XIoT Security report was created to help decision makers understand the threat and vulnerability landscape affecting not only the industrial sector but also healthcare and commercial.
Interestingly enough the data in the first half of 2022 report that we’re sharing today for the first time reflects this expansion into the Extended Internet of Things (XIoT). Among the 747 XIoT vulnerabilities (86 affected vendors) published in the 1H 2022, we’re seeing for the first time real movement in the number of published vulnerabilities around enterprise IoT and progress in updating firmware and providing remediations for these components deep within cyber physical systems.
Firmware updates traditionally lag behind software patching and mitigations, for example, but in this report we’re seeing updates for both almost on par with each other. This indicates that enterprise risk managers are looking at connected embedded systems that make up the XIoT, assessing the risk to the systems, and are making progress and patching and updating them.
We hope you find the State of XIoT Security report an important resource that you will share with security executives and the board, as well as with network analysts, engineers, asset owners and operators, and managers responsible for the security of enterprise IoT.
Let’s look at some key findings:
You can see that OT vulnerabilities still dominate Team82’s dataset for the 1H 2022, but it’s noteworthy that the percentage of IoT vulnerabilities has almost doubled since our last report, especially impacting connected smart devices, routers and other networking gear, and cameras—all of which if compromised may afford an attacker deeper access to the enterprise network.
Most of the published XIoT vulnerabilities in the 1H 2022 are either critical (19%) or high severity (46%). And of those severe bugs, many affect the availability of XIoT devices by enabling code execution or denial-of-service attacks.
With the rise in cyber-physical systems across industries, we’re starting to see the expected spikes in published firmware vulnerabilities in IoT devices, as well as the internet of medical things (IoMT), and operational technology devices at Levels 1 and 2 of the Purdue Model for ICS.
Below, you can see that for the 1H 2022, the number of published firmware vulnerabilities is almost on par with software vulnerabilities, a significant reversal from the 2H 2021 report when there was an almost 2-to-1 disparity between software and firmware vulnerabilities.
Meanwhile, vulnerabilities in connected IoT devices—largely firmware issues—trail only Operations Management and Basic Control devices. Vulnerabilities in these products, which include Historian and OPC servers, as well as field devices, for example, are predominantly software-based.
Team82’s 1H 2022 dataset indicates that vendors provided full or partial remediation for 91% of published vulnerabilities.
Breaking that down by software and firmware vulnerabilities, you can see the gains made in firmware fixes for the first half of the year compared to our last report.
When a software patch or firmware update isn’t immediately available, basic security practices should be adhered to in order to blunt the impact of vulnerabilities. Here are the top mitigation steps from Team82’s 1H 2022 dataset.
CWE-257: Storing Passwords in a Recoverable Format
RND encrypts passwords with a hardcoded weak secret key and returns the passwords in plaintext. If the server were compromised, an attacker could gain all the plaintext passwords and decrypt them.
No patches have been supplied by the vendor at this time. To mitigate risk, network administrators should limit access to the wireless management environments that use these affected products, allowing a limited set of trusted users and their authenticated clients to manage Ruckus infrastructure via a secure protocol such as HTTPS or SSH.
CVSS v3: 5.3
CWE-321: Use of Hard-coded Cryptographic Key
A built-in user called sshuser, with root privileges, exists on the RND platform. Both public and private ssh keys exist in the sshuser home directory. Anyone with the private key can access an RND server as sshuser.
No patches have been supplied by the vendor at this time. To mitigate risk, network administrators should limit access to the wireless management environments that use these affected products, allowing a limited set of trusted users and their authenticated clients to manage Ruckus infrastructure via a secure protocol such as HTTPS or SSH.
CVSS v3: 10.0
CWE-259: Use of Hard-coded Password
RND includes a jailed environment to allow users to configure devices without complete shell access to the underlying operating system. The jailed environment includes a built-in jailbreak for technicians to elevate privileges. The jailbreak requires a weak password that is hardcoded into the environment. Anyone with this password can access an RND server with root permissions.
No patches have been supplied by the vendor at this time. To mitigate risk, network administrators should limit access to the wireless management environments that use these affected products, allowing a limited set of trusted users and their authenticated clients to manage Ruckus infrastructure via a secure protocol such as HTTPS or SSH.
CVSS v3: 8.2
CWE-321: Use of Hard-coded Cryptographic Key
RND uses a secret key on the backend web server to ensure that session JWTs are valid. This secret key is hardcoded into the web server. Anyone with knowledge of the secret key could create a valid JWT, thus bypassing the typical authentication to access the server with administrator privileges.
No patches have been supplied by the vendor at this time. To mitigate risk, network administrators should limit access to the wireless management environments that use these affected products, allowing a limited set of trusted users and their authenticated clients to manage Ruckus infrastructure via a secure protocol such as HTTPS or SSH.
CVSS v3: 9.8
CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
An authenticated vSZ user supplies an IP address as an argument to be run in an OS command, but this IP address is not sanitized. A user could supply other commands instead of an IP address to achieve RCE.
No patches have been supplied by the vendor at this time. To mitigate risk, network administrators should limit access to the wireless management environments that use these affected products, allowing a limited set of trusted users and their authenticated clients to manage Ruckus infrastructure via a secure protocol such as HTTPS or SSH.
CVSS v3: 9.0
