CVE-2021-37208 Detail

CVE-2021-37208

Score / Severity

9.6

Critical

CVE Descriptions

A vulnerability has been identified in RUGGEDCOM i800, RUGGEDCOM i800NC, RUGGEDCOM i801, RUGGEDCOM i801NC, RUGGEDCOM i802, RUGGEDCOM i802NC, RUGGEDCOM i803, RUGGEDCOM i803NC, RUGGEDCOM M2100, RUGGEDCOM M2100F, RUGGEDCOM M2100NC, RUGGEDCOM M2200, RUGGEDCOM M2200F, RUGGEDCOM M2200NC, RUGGEDCOM M969, RUGGEDCOM M969F, RUGGEDCOM M969NC, RUGGEDCOM RMC30, RUGGEDCOM RMC30NC, RUGGEDCOM RMC8388 V4.X, RUGGEDCOM RMC8388 V5.X, RUGGEDCOM RMC8388NC V4.X, RUGGEDCOM RMC8388NC V5.X, RUGGEDCOM RP110, RUGGEDCOM RP110NC, RUGGEDCOM RS1600, RUGGEDCOM RS1600F, RUGGEDCOM RS1600FNC, RUGGEDCOM RS1600NC, RUGGEDCOM RS1600T, RUGGEDCOM RS1600TNC, RUGGEDCOM RS400, RUGGEDCOM RS400F, RUGGEDCOM RS400NC, RUGGEDCOM RS401, RUGGEDCOM RS401NC, RUGGEDCOM RS416, RUGGEDCOM RS416F, RUGGEDCOM RS416NC, RUGGEDCOM RS416NCv2 V4.X, RUGGEDCOM RS416NCv2 V5.X, RUGGEDCOM RS416P, RUGGEDCOM RS416PF, RUGGEDCOM RS416PNC, RUGGEDCOM RS416PNCv2 V4.X, RUGGEDCOM RS416PNCv2 V5.X, RUGGEDCOM RS416Pv2 V4.X, RUGGEDCOM RS416Pv2 V5.X, RUGGEDCOM RS416v2 V4.X, RUGGEDCOM RS416v2 V5.X, RUGGEDCOM RS8000, RUGGEDCOM RS8000A, RUGGEDCOM RS8000ANC, RUGGEDCOM RS8000H, RUGGEDCOM RS8000HNC, RUGGEDCOM RS8000NC, RUGGEDCOM RS8000T, RUGGEDCOM RS8000TNC, RUGGEDCOM RS900, RUGGEDCOM RS900 (32M) V4.X, RUGGEDCOM RS900 (32M) V5.X, RUGGEDCOM RS900F, RUGGEDCOM RS900G, RUGGEDCOM RS900G (32M) V4.X, RUGGEDCOM RS900G (32M) V5.X, RUGGEDCOM RS900GF, RUGGEDCOM RS900GNC, RUGGEDCOM RS900GNC(32M) V4.X, RUGGEDCOM RS900GNC(32M) V5.X, RUGGEDCOM RS900GP, RUGGEDCOM RS900GPF, RUGGEDCOM RS900GPNC, RUGGEDCOM RS900L, RUGGEDCOM RS900LNC, RUGGEDCOM RS900M-GETS-C01, RUGGEDCOM RS900M-GETS-XX, RUGGEDCOM RS900M-STND-C01, RUGGEDCOM RS900M-STND-XX, RUGGEDCOM RS900MNC-GETS-C01, RUGGEDCOM RS900MNC-GETS-XX, RUGGEDCOM RS900MNC-STND-XX, RUGGEDCOM RS900MNC-STND-XX-C01, RUGGEDCOM RS900NC, RUGGEDCOM RS900NC(32M) V4.X, RUGGEDCOM RS900NC(32M) V5.X, RUGGEDCOM RS900W, RUGGEDCOM RS910, RUGGEDCOM RS910L, RUGGEDCOM RS910LNC, RUGGEDCOM RS910NC, RUGGEDCOM RS910W, RUGGEDCOM RS920L, RUGGEDCOM RS920LNC, RUGGEDCOM RS920W, RUGGEDCOM RS930L, RUGGEDCOM RS930LNC, RUGGEDCOM RS930W, RUGGEDCOM RS940G, RUGGEDCOM RS940GF, RUGGEDCOM RS940GNC, RUGGEDCOM RS969, RUGGEDCOM RS969NC, RUGGEDCOM RSG2100, RUGGEDCOM RSG2100 (32M) V4.X, RUGGEDCOM RSG2100 (32M) V5.X, RUGGEDCOM RSG2100F, RUGGEDCOM RSG2100NC, RUGGEDCOM RSG2100NC(32M) V4.X, RUGGEDCOM RSG2100NC(32M) V5.X, RUGGEDCOM RSG2100P, RUGGEDCOM RSG2100PF, RUGGEDCOM RSG2100PNC, RUGGEDCOM RSG2200, RUGGEDCOM RSG2200F, RUGGEDCOM RSG2200NC, RUGGEDCOM RSG2288 V4.X, RUGGEDCOM RSG2288 V5.X, RUGGEDCOM RSG2288NC V4.X, RUGGEDCOM RSG2288NC V5.X, RUGGEDCOM RSG2300 V4.X, RUGGEDCOM RSG2300 V5.X, RUGGEDCOM RSG2300F, RUGGEDCOM RSG2300NC V4.X, RUGGEDCOM RSG2300NC V5.X, RUGGEDCOM RSG2300P V4.X, RUGGEDCOM RSG2300P V5.X, RUGGEDCOM RSG2300PF, RUGGEDCOM RSG2300PNC V4.X, RUGGEDCOM RSG2300PNC V5.X, RUGGEDCOM RSG2488 V4.X, RUGGEDCOM RSG2488 V5.X, RUGGEDCOM RSG2488F, RUGGEDCOM RSG2488NC V4.X, RUGGEDCOM RSG2488NC V5.X, RUGGEDCOM RSG907R, RUGGEDCOM RSG908C, RUGGEDCOM RSG909R, RUGGEDCOM RSG910C, RUGGEDCOM RSG920P V4.X, RUGGEDCOM RSG920P V5.X, RUGGEDCOM RSG920PNC V4.X, RUGGEDCOM RSG920PNC V5.X, RUGGEDCOM RSL910, RUGGEDCOM RSL910NC, RUGGEDCOM RST2228, RUGGEDCOM RST2228P, RUGGEDCOM RST916C, RUGGEDCOM RST916P. Improper neutralization of special characters on the web server configuration page could allow an attacker, in a privileged position, to retrieve sensitive information via cross-site scripting.

CVE Informations

Related Weaknesses

CWE-ID	Weakness Name	Source
CWE-79	Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Metrics

Metrics	Score	Severity	CVSS Vector	Source
V3.1	9.6	CRITICAL	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:H/E:P/RL:T/RC:C More informations 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. Required Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator. 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. Changed An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities. 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. Low There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component. 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. Exploit Code Maturity This metric measures the likelihood of the vulnerability being attacked, and is typically based on the current state of exploit techniques, exploit code availability, or active, “in-the-wild” exploitation. Proof-of-Concept Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker. Remediation Level The Remediation Level of a vulnerability is an important factor for prioritization. Temporary fix There is an official but temporary fix available. This includes instances where the vendor issues a temporary hotfix, tool, or workaround. Report Confidence This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Confirmed Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the 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.
V3.1	9.6	CRITICAL	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:H More informations 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. Required Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator. 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. Changed An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities. 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. Low There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component. 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]
V3.1	5.4	MEDIUM	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N More informations 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. Low The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources. 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. Required Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator. 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. Changed An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities. 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. Low There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component. Integrity Impact This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Low Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component. Availability Impact This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. None There is no impact to availability within the impacted component. 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	3.5		AV:N/AC:M/Au:S/C:N/I:P/A:N	[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 >> Version *

Siemens>>Ruggedcom_ros >> Version 4.3.4 (Open CPE detail)
Siemens>>Ruggedcom_ros >> Version 4.3.7 (Open CPE detail)
Siemens>>Ruggedcom_ros >> Version 4.3.8 (Open CPE detail)
Siemens>>Ruggedcom_ros >> Version 5.0.1 (Open CPE detail)
Siemens>>Ruggedcom_ros >> Version 5.6.0 (Open CPE detail)

Siemens>>Ruggedcom_i800 >> Version -

Siemens>>Ruggedcom_i800 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_i801 >> Version -

Siemens>>Ruggedcom_i801 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_i802 >> Version -

Siemens>>Ruggedcom_i802 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_i803 >> Version -

Siemens>>Ruggedcom_i803 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_m2100 >> Version -

Siemens>>Ruggedcom_m2100 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_m2200 >> Version -

Siemens>>Ruggedcom_m2200 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_m969 >> Version -

Siemens>>Ruggedcom_m969 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rmc >> Version -

Siemens>>Ruggedcom_rmc >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rmc20 >> Version -

Siemens>>Ruggedcom_rmc20 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rmc30 >> Version -

Siemens>>Ruggedcom_rmc30 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rmc40 >> Version -

Siemens>>Ruggedcom_rmc40 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rmc41 >> Version -

Siemens>>Ruggedcom_rmc41 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rp110 >> Version -

Siemens>>Ruggedcom_rp110 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs400 >> Version -

Siemens>>Ruggedcom_rs400 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs401 >> Version -

Siemens>>Ruggedcom_rs401 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs416 >> Version -

Siemens>>Ruggedcom_rs416 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs8000 >> Version -

Siemens>>Ruggedcom_rs8000 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs8000a >> Version -

Siemens>>Ruggedcom_rs8000a >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs8000h >> Version -

Siemens>>Ruggedcom_rs8000h >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs8000t >> Version -

Siemens>>Ruggedcom_rs8000t >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs900gp >> Version -

Siemens>>Ruggedcom_rs900gp >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs900l >> Version -

Siemens>>Ruggedcom_rs900l >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs900w >> Version -

Siemens>>Ruggedcom_rs900w >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs910 >> Version -

Siemens>>Ruggedcom_rs910 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs910l >> Version -

Siemens>>Ruggedcom_rs910l >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs910w >> Version -

Siemens>>Ruggedcom_rs910w >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs920l >> Version -

Siemens>>Ruggedcom_rs920l >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs920w >> Version -

Siemens>>Ruggedcom_rs920w >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs930l >> Version -

Siemens>>Ruggedcom_rs930l >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs930w >> Version -

Siemens>>Ruggedcom_rs930w >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs940g >> Version -

Siemens>>Ruggedcom_rs940g >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs969 >> Version -

Siemens>>Ruggedcom_rs969 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg2100p >> Version -

Siemens>>Ruggedcom_rsg2100p >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg2200 >> Version -

Siemens>>Ruggedcom_rsg2200 >> Version - (Open CPE detail)

Configuraton 0

Siemens>>Ruggedcom_ros >> Version To (excluding) 5.6.0

Siemens>>Ruggedcom_ros >> Version 4.3.4 (Open CPE detail)
Siemens>>Ruggedcom_ros >> Version 4.3.7 (Open CPE detail)
Siemens>>Ruggedcom_ros >> Version 4.3.8 (Open CPE detail)
Siemens>>Ruggedcom_ros >> Version 5.0.1 (Open CPE detail)

Siemens>>Ruggedcom_rmc8388 >> Version -

Siemens>>Ruggedcom_rmc8388 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs416v2 >> Version -

Siemens>>Ruggedcom_rs416v2 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs900 >> Version -

Siemens>>Ruggedcom_rs900 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rs900g >> Version -

Siemens>>Ruggedcom_rs900g >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg2100 >> Version -

Siemens>>Ruggedcom_rsg2100 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg2288 >> Version -

Siemens>>Ruggedcom_rsg2288 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg2300 >> Version -

Siemens>>Ruggedcom_rsg2300 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg2300p >> Version -

Siemens>>Ruggedcom_rsg2300p >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg2488 >> Version -

Siemens>>Ruggedcom_rsg2488 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg907r >> Version -

Siemens>>Ruggedcom_rsg907r >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg908c >> Version -

Siemens>>Ruggedcom_rsg908c >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg909r >> Version -

Siemens>>Ruggedcom_rsg909r >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg910c >> Version -

Siemens>>Ruggedcom_rsg910c >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsg920p >> Version -

Siemens>>Ruggedcom_rsg920p >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rsl910 >> Version -

Siemens>>Ruggedcom_rsl910 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rst2228 >> Version -

Siemens>>Ruggedcom_rst2228 >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rst2228p >> Version -

Siemens>>Ruggedcom_rst2228p >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rst916c >> Version -

Siemens>>Ruggedcom_rst916c >> Version - (Open CPE detail)

Siemens>>Ruggedcom_rst916p >> Version -

Siemens>>Ruggedcom_rst916p >> Version - (Open CPE detail)

References

https://cert-portal.siemens.com/productcert/pdf/ssa-256353.pdf
Tags : Patch, Vendor Advisory

CVE-2021-37208 : Detail

CVE-2021-37208

CVE Descriptions

CVE Informations

Related Weaknesses

Metrics

Base: Exploitabilty Metrics

Base: Scope Metrics

Base: Impact Metrics

Temporal Metrics

Environmental Metrics

Base: Exploitabilty Metrics

Base: Scope Metrics

Base: Impact Metrics

Temporal Metrics

Environmental Metrics

Base: Exploitabilty Metrics

Base: Scope Metrics

Base: Impact Metrics

Temporal Metrics

Environmental Metrics

EPSS

EPSS Score

EPSS Percentile

Products Mentioned

Configuraton 0

Configuraton 0

References