CVE-2021-31895 : Detail

CVE-2021-31895

9.8
/
Critical
Overflow
0.54%V3
Network
2021-07-13
09h02 +00:00
2021-07-13
09h02 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

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.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow.
CWE-787 Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 9.8 CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 [email protected]
V2 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Siemens>>Ruggedcom_ros_i800 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_i800 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_i801 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_i801 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_i802 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_i802 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_i803 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_i803 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_m969 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_m969 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_m2100 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_m2100 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_m2200 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_m2200 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rmc >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rmc >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rmc20 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rmc20 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rmc30 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rmc30 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rmc40 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rmc40 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rmc41 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rmc41 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rmc8388 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rmc8388 >> Version From (including) 5.0.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rmc8388 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rp110 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rp110 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs400 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs400 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs401 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs401 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs416 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs416 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs416v2 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rs416v2 >> Version From (including) 5.5.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rs416v2 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs900 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rs900 >> Version From (including) 5.0.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rs900 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs900g >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rs900g >> Version From (including) 5.0.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rs900g >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs900gp >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs900gp >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs900l >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs900l >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs900w >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs900w >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs910 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs910 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs910l >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs910l >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs910w >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs910w >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs920l >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs920l >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs920w >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs920w >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs930l >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs930l >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs930w >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs930w >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs940g >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs940g >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs969 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs969 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs8000 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs8000 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs8000a >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs8000a >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs8000h >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs8000h >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rs8000t >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rs8000t >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg900 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rsg900 >> Version From (including) 5.5.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rsg900 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg900c >> Version To (excluding) 5.5.4

Siemens>>Ruggedcom_rsg900c >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg900g >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rsg900g >> Version From (including) 5.0.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rsg900g >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg900r >> Version To (excluding) 5.5.4

Siemens>>Ruggedcom_rsg900r >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg920p >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rsg920p >> Version From (including) 5.0.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rsg920p >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg2100 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rsg2100 >> Version From (including) 5.0.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rsg2100 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg2100p >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rsg2100p >> Version From (including) 5.0.0 To (excluding) 5.3.4

Siemens>>Ruggedcom_rsg2100p >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg2200 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_rsg2200 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg2288 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rsg2288 >> Version From (including) 5.0.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rsg2288 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg2300 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rsg2300 >> Version From (including) 5.0.0 To (excluding) 5.3.4

Siemens>>Ruggedcom_rsg2300 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg2300p >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rsg2300p >> Version From (including) 5.5.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rsg2300p >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsg2488 >> Version To (excluding) 4.3.7

Siemens>>Ruggedcom_ros_rsg2488 >> Version From (including) 5.0.0 To (excluding) 5.5.4

Siemens>>Ruggedcom_rsg2488 >> Version -

Configuraton 0

Siemens>>Ruggedcom_ros_rsl910 >> Version To (excluding) 5.5.4

    Siemens>>Ruggedcom_rsl910 >> Version -

    Configuraton 0

    Siemens>>Ruggedcom_ros_rst916c >> Version To (excluding) 5.5.4

    Siemens>>Ruggedcom_rst916c >> Version -

    Configuraton 0

    Siemens>>Ruggedcom_ros_rst916p >> Version To (excluding) 5.5.4

    Siemens>>Ruggedcom_rst916p >> Version -

    Configuraton 0

    Siemens>>Ruggedcom_ros_rst2228 >> Version To (excluding) 5.5.4

    Siemens>>Ruggedcom_rst2228 >> Version -

    References