CVE-2024-41977
CVE Descriptions
CVE Informations
Related Weaknesses
| Weakness Name | Source | |
|---|---|---|
| Exposure of Data Element to Wrong Session The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session. |
Metrics
| Metrics | Score | Severity | CVSS Vector | Source |
|---|---|---|---|---|
| V4.0 | 7.3 | HIGH |
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
More informations
Base: Exploitabilty MetricsThe Exploitability metrics reflect the characteristics of the “thing that is vulnerable”, which we refer to formally as the vulnerable system. Attack Vector This metric reflects the context by which vulnerability exploitation is possible. Network The vulnerable system 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 captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. High The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques. The attacker must have additional methods available to bypass security measures in place. For example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful. Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target. Attack Requirements This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack. None The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability. Privileges Required This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. Low The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged 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 system. Active Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability. Examples include: importing a file into a vulnerable system in a specific manner placing files into a specific directory prior to executing code submitting a specific string into a web application (e.g. reflected or self XSS) dismiss or accept prompts or security warnings prior to taking an action (e.g. opening/editing a file, connecting a device). Base: Impact MetricsThe Impact metrics capture the effects of a successfully exploited vulnerability. 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 managed by the system due to a successfully exploited vulnerability. High There is a total loss of confidentiality, resulting in all information within the Vulnerable System 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. 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 Vulnerable System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Vulnerable System. Availability Impact This metric measures the impact to the availability of the impacted system 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 Vulnerable System; 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 Vulnerable System (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). Sub Confidentiality Impact Negligible There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System. Sub Integrity Impact None There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System. Sub Availability Impact None There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System. Threat MetricsThe Threat metrics measure the current state of exploit techniques or code availability for a vulnerability. Environmental MetricsThese metrics enable the consumer analyst to customize the resulting score depending on the importance of the affected IT asset to a user’s organization, measured in terms of complementary/alternative security controls in place, Confidentiality, Integrity, and Availability. The metrics are the modified equivalent of Base metrics and are assigned values based on the system placement within organizational infrastructure. Supplemental MetricsSupplemental metric group provides new metrics that describe and measure additional extrinsic attributes of a vulnerability. While the assessment of Supplemental metrics is provisioned by the provider, the usage and response plan of each metric within the Supplemental metric group is determined by the consumer. |
|
| V3.1 | 7.1 | HIGH |
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
More informations
Base: Exploitabilty MetricsThe 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. High successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. 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 MetricsThe 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 MetricsThe 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 MetricsThe 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. Official fix A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available. 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 MetricsThese 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 | 8 | HIGH |
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
More informations
Base: Exploitabilty MetricsThe 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 MetricsThe 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 MetricsThe 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 MetricsThe 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 MetricsThese 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 | 7.1 | HIGH |
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
More informations
Base: Exploitabilty MetricsThe 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. High successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. 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 MetricsThe 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 MetricsThe 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 MetricsThe 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 MetricsThese 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] |
EPSS
EPSS Score
EPSS Percentile
Products Mentioned
Configuraton 0
Siemens>>Ruggedcom_rm1224_lte\(4g\)_eu_firmware >> Version To (excluding) 8.1
- Siemens>>Ruggedcom_rm1224_lte\(4g\)_eu_firmware >> Version - (Open CPE detail)
Siemens>>Ruggedcom_rm1224_lte\(4g\)_eu >> Version -
- Siemens>>Ruggedcom_rm1224_lte\(4g\)_eu >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Ruggedcom_rm1224_lte\(4g\)_nam_firmware >> Version To (excluding) 8.1
- Siemens>>Ruggedcom_rm1224_lte\(4g\)_nam_firmware >> Version - (Open CPE detail)
Siemens>>Ruggedcom_rm1224_lte\(4g\)_nam >> Version -
- Siemens>>Ruggedcom_rm1224_lte\(4g\)_nam >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m804pb_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m804pb_firmware >> Version - (Open CPE detail)
- Siemens>>Scalance_m804pb_firmware >> Version 7.1.2 (Open CPE detail)
Siemens>>Scalance_m804pb >> Version -
- Siemens>>Scalance_m804pb >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m826-2_shdsl-router_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m826-2_shdsl-router_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_m826-2_shdsl-router >> Version -
- Siemens>>Scalance_m826-2_shdsl-router >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m874-2_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m874-2_firmware >> Version - (Open CPE detail)
- Siemens>>Scalance_m874-2_firmware >> Version 7.1.2 (Open CPE detail)
Siemens>>Scalance_m874-2 >> Version -
- Siemens>>Scalance_m874-2 >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m874-3_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m874-3_firmware >> Version - (Open CPE detail)
- Siemens>>Scalance_m874-3_firmware >> Version 7.1.2 (Open CPE detail)
Siemens>>Scalance_m874-3 >> Version -
- Siemens>>Scalance_m874-3 >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m876-3_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m876-3_firmware >> Version - (Open CPE detail)
- Siemens>>Scalance_m876-3_firmware >> Version 7.1.2 (Open CPE detail)
Siemens>>Scalance_m876-3 >> Version -
- Siemens>>Scalance_m876-3 >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m876-4_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m876-4_firmware >> Version - (Open CPE detail)
- Siemens>>Scalance_m876-4_firmware >> Version 7.1.2 (Open CPE detail)
Siemens>>Scalance_m876-4 >> Version -
- Siemens>>Scalance_m876-4 >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m874-3_3g-router_\(cn\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m874-3_3g-router_\(cn\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_m874-3_3g-router_\(cn\) >> Version -
- Siemens>>Scalance_m874-3_3g-router_\(cn\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m876-3_\(rok\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m876-3_\(rok\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_m876-3_\(rok\) >> Version -
- Siemens>>Scalance_m876-3_\(rok\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m876-4_\(eu\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m876-4_\(eu\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_m876-4_\(eu\) >> Version -
- Siemens>>Scalance_m876-4_\(eu\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m876-4_\(nam\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m876-4_\(nam\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_m876-4_\(nam\) >> Version -
- Siemens>>Scalance_m876-4_\(nam\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_mum853-1_\(a1\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_mum853-1_\(a1\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_mum853-1_\(a1\) >> Version -
- Siemens>>Scalance_mum853-1_\(a1\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_mum853-1_\(b1\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_mum853-1_\(b1\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_mum853-1_\(b1\) >> Version -
- Siemens>>Scalance_mum853-1_\(b1\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_mum853-1_\(eu\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_mum853-1_\(eu\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_mum853-1_\(eu\) >> Version -
- Siemens>>Scalance_mum853-1_\(eu\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_mum856-1_\(a1\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_mum856-1_\(a1\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_mum856-1_\(a1\) >> Version -
- Siemens>>Scalance_mum856-1_\(a1\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_mum856-1_\(b1\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_mum856-1_\(b1\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_mum856-1_\(b1\) >> Version -
- Siemens>>Scalance_mum856-1_\(b1\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_mum856-1_\(cn\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_mum856-1_\(cn\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_mum856-1_\(cn\) >> Version -
- Siemens>>Scalance_mum856-1_\(cn\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_mum856-1_\(eu\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_mum856-1_\(eu\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_mum856-1_\(eu\) >> Version -
- Siemens>>Scalance_mum856-1_\(eu\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_mum856-1_\(row\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_mum856-1_\(row\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_mum856-1_\(row\) >> Version -
- Siemens>>Scalance_mum856-1_\(row\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_s615_eec_lan-router_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_s615_eec_lan-router_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_s615_eec_lan-router >> Version -
- Siemens>>Scalance_s615_eec_lan-router >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_s615_lan-router_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_s615_lan-router_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_s615_lan-router >> Version -
- Siemens>>Scalance_s615_lan-router >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m812-1_\(annex_a\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m812-1_\(annex_a\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_m812-1_\(annex_a\) >> Version -
- Siemens>>Scalance_m812-1_\(annex_a\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m812-1_\(annex_b\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m812-1_\(annex_b\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_m812-1_\(annex_b\) >> Version -
- Siemens>>Scalance_m812-1_\(annex_b\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m816-1_\(annex_a\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m816-1_\(annex_a\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_m816-1_\(annex_a\) >> Version -
- Siemens>>Scalance_m816-1_\(annex_a\) >> Version - (Open CPE detail)
Configuraton 0
Siemens>>Scalance_m816-1_\(annex_b\)_firmware >> Version To (excluding) 8.1
- Siemens>>Scalance_m816-1_\(annex_b\)_firmware >> Version - (Open CPE detail)
Siemens>>Scalance_m816-1_\(annex_b\) >> Version -
- Siemens>>Scalance_m816-1_\(annex_b\) >> Version - (Open CPE detail)
