CVE-2021-31895 in RuggedCom ROS
Summary
by MITRE • 07/13/2021
A vulnerability has been identified in RUGGEDCOM ROS M2100 (All versions < V4.3.7), RUGGEDCOM ROS M2200 (All versions < V4.3.7), RUGGEDCOM ROS M969 (All versions < V4.3.7), RUGGEDCOM ROS RMC (All versions < V4.3.7), RUGGEDCOM ROS RMC20 (All versions < V4.3.7), RUGGEDCOM ROS RMC30 (All versions < V4.3.7), RUGGEDCOM ROS RMC40 (All versions < V4.3.7), RUGGEDCOM ROS RMC41 (All versions < V4.3.7), RUGGEDCOM ROS RMC8388 V4.X (All versions < V4.3.7), RUGGEDCOM ROS RMC8388 V5.X (All versions < V5.5.4), RUGGEDCOM ROS RP110 (All versions < V4.3.7), RUGGEDCOM ROS RS400 (All versions < V4.3.7), RUGGEDCOM ROS RS401 (All versions < V4.3.7), RUGGEDCOM ROS RS416 (All versions < V4.3.7), RUGGEDCOM ROS RS416v2 V4.X (All versions < V4.3.7), RUGGEDCOM ROS RS416v2 V5.X (All versions < 5.5.4), RUGGEDCOM ROS RS8000 (All versions < V4.3.7), RUGGEDCOM ROS RS8000A (All versions < V4.3.7), RUGGEDCOM ROS RS8000H (All versions < V4.3.7), RUGGEDCOM ROS RS8000T (All versions < V4.3.7), RUGGEDCOM ROS RS900 (32M) V4.X (All versions < V4.3.7), RUGGEDCOM ROS RS900 (32M) V5.X (All versions < V5.5.4), RUGGEDCOM ROS RS900G (All versions < V4.3.7), RUGGEDCOM ROS RS900G (32M) V4.X (All versions < V4.3.7), RUGGEDCOM ROS RS900G (32M) V5.X (All versions < V5.5.4), RUGGEDCOM ROS RS900GP (All versions < V4.3.7), RUGGEDCOM ROS RS900L (All versions < V4.3.7), RUGGEDCOM ROS RS900W (All versions < V4.3.7), RUGGEDCOM ROS RS910 (All versions < V4.3.7), RUGGEDCOM ROS RS910L (All versions < V4.3.7), RUGGEDCOM ROS RS910W (All versions < V4.3.7), RUGGEDCOM ROS RS920L (All versions < V4.3.7), RUGGEDCOM ROS RS920W (All versions < V4.3.7), RUGGEDCOM ROS RS930L (All versions < V4.3.7), RUGGEDCOM ROS RS930W (All versions < V4.3.7), RUGGEDCOM ROS RS940G (All versions < V4.3.7), RUGGEDCOM ROS RS969 (All versions < V4.3.7), RUGGEDCOM ROS RSG2100 (32M) V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG2100 (32M) V5.X (All versions < V5.5.4), RUGGEDCOM ROS RSG2100 V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG2100P (All versions < V4.3.7), RUGGEDCOM ROS RSG2100P (32M) V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG2100P (32M) V5.X (All versions < V5.5.4), RUGGEDCOM ROS RSG2200 (All versions < V4.3.7), RUGGEDCOM ROS RSG2288 V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG2288 V5.X (All versions < V5.5.4), RUGGEDCOM ROS RSG2300 V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG2300 V5.X (All versions < V5.5.4), RUGGEDCOM ROS RSG2300P V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG2300P V5.X (All versions < V5.5.4), RUGGEDCOM ROS RSG2488 V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG2488 V5.X (All versions < V5.5.4), RUGGEDCOM ROS RSG900 V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG900 V5.X (All versions < V5.5.4), RUGGEDCOM ROS RSG900C (All versions < V5.5.4), RUGGEDCOM ROS RSG900G V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG900G V5.X (All versions < V5.5.4), RUGGEDCOM ROS RSG900R (All versions < V5.5.4), RUGGEDCOM ROS RSG920P V4.X (All versions < V4.3.7), RUGGEDCOM ROS RSG920P V5.X (All versions < V5.5.4), RUGGEDCOM ROS RSL910 (All versions < V5.5.4), RUGGEDCOM ROS RST2228 (All versions < V5.5.4), RUGGEDCOM ROS RST916C (All versions < V5.5.4), RUGGEDCOM ROS RST916P (All versions < V5.5.4), RUGGEDCOM ROS i800 (All versions < V4.3.7), RUGGEDCOM ROS i801 (All versions < V4.3.7), RUGGEDCOM ROS i802 (All versions < V4.3.7), RUGGEDCOM ROS i803 (All versions < V4.3.7). The DHCP client in affected devices fails to properly sanitize incoming DHCP packets. This could allow an unauthenticated remote attacker to cause memory to be overwritten, potentially allowing remote code execution.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 05/13/2025
This vulnerability resides within the Dynamic Host Configuration Protocol client implementation of numerous RUGGEDCOM ROS series devices, representing a critical security flaw that affects a broad range of industrial networking equipment. The issue stems from inadequate input validation within the DHCP client component, which fails to properly sanitize incoming DHCP packets before processing them. This deficiency creates a potential attack surface where malicious actors can manipulate DHCP responses to overwrite memory locations within the device's operating system, thereby compromising system integrity and potentially enabling unauthorized code execution.
The technical nature of this vulnerability aligns with CWE-129, which describes improper validation of array index values, and CWE-787, which addresses out-of-bounds write conditions. These weaknesses specifically manifest when the DHCP client processes malformed or crafted responses from rogue DHCP servers on the network. The vulnerability's remote exploitability means that attackers do not require physical access or authentication credentials to target affected devices, making it particularly dangerous in industrial environments where network infrastructure devices often operate in unsecured or hostile network conditions. The memory corruption resulting from this flaw can lead to arbitrary code execution, system crashes, or complete device compromise, potentially disrupting critical network operations.
The operational impact of this vulnerability extends beyond simple system instability, particularly within industrial control systems and critical infrastructure environments where RUGGEDCOM devices are commonly deployed. Attackers could leverage this vulnerability to gain persistent access to network segments, potentially enabling lateral movement throughout the facility's network infrastructure. The widespread nature of affected models means that organizations with extensive deployments of these devices face significant risk exposure, as the vulnerability affects multiple device families across various generations. This flaw particularly threatens operational technology environments where device uptime and security are paramount, as exploitation could lead to service disruptions, data integrity issues, or even safety hazards in environments where network infrastructure directly supports critical operations.
Organizations should immediately implement mitigation strategies including network segmentation to isolate affected devices, deployment of network access controls to restrict DHCP server access, and implementation of DHCP snooping mechanisms to prevent unauthorized DHCP responses. The most effective long-term solution involves upgrading all affected devices to the patched versions specified in the vendor advisories, which address the input validation flaws in the DHCP client implementation. Network administrators should also consider implementing monitoring solutions to detect anomalous DHCP traffic patterns that might indicate exploitation attempts, while maintaining awareness of the ATT&CK framework's T1071.004 technique for application layer protocol: dns, which could be leveraged by attackers to further exploit the compromised devices. Additionally, organizations should conduct comprehensive vulnerability assessments to identify any other potentially vulnerable network infrastructure components that might be at risk from similar memory corruption vulnerabilities.