CVE-2022-38465 : Detail

CVE-2022-38465

9.3
/
Critical
A04-Insecure Design
0.04%V3
Local
2022-10-10
22h00 +00:00
2024-08-03
10h54 +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 SIMATIC Drive Controller family (All versions < V2.9.2), SIMATIC ET 200SP Open Controller CPU 1515SP PC (incl. SIPLUS variants) (All versions), SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants) (All versions < V21.9), SIMATIC S7-1200 CPU family (incl. SIPLUS variants) (All versions < V4.5.0), SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions < V2.9.2), SIMATIC S7-1500 Software Controller (All versions < V21.9), SIMATIC S7-PLCSIM Advanced (All versions < V4.0), SINUMERIK MC (All versions < V6.21), SINUMERIK ONE (All versions < V6.21). Affected products protect the built-in global private key in a way that cannot be considered sufficient any longer. The key is used for the legacy protection of confidential configuration data and the legacy PG/PC and HMI communication. This could allow attackers to discover the private key of a CPU product family by an offline attack against a single CPU of the family. Attackers could then use this knowledge to extract confidential configuration data from projects that are protected by that key or to perform attacks against legacy PG/PC and HMI communication.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-522 Insufficiently Protected Credentials
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 9.3 CRITICAL CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C

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.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

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.

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.

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.

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 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 7.8 HIGH CVSS:3.1/AV:L/AC:L/PR:L/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.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

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.

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]
V3.1 9.3 CRITICAL CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

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.

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.

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]

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>>Simatic_et_200_sp_open_controller_cpu_1515sp_pc2_firmware >> Version To (excluding) 21.9

  • Siemens>>Simatic_et_200_sp_open_controller_cpu_1515sp_pc2_firmware >> Version - (Open CPE detail)
  • Siemens>>Simatic_et_200_sp_open_controller_cpu_1515sp_pc2_firmware >> Version 2.7 (Open CPE detail)

Siemens>>Simatic_et_200_open_controller_cpu_1515sp_pc2 >> Version -

Configuraton 0

Siemens>>Simatic_et_200_sp_open_controller_cpu_1515sp_pc_firmware >> Version *

  • Siemens>>Simatic_et_200_sp_open_controller_cpu_1515sp_pc_firmware >> Version - (Open CPE detail)
  • Siemens>>Simatic_et_200_sp_open_controller_cpu_1515sp_pc_firmware >> Version 2.1.6 (Open CPE detail)

Siemens>>Simatic_et_200_open_controller_cpu_1515sp_pc >> Version -

Configuraton 0

Siemens>>Simatic_drive_controller_cpu_1504d_tf_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_drive_controller_cpu_1504d_tf >> Version -

Configuraton 0

Siemens>>Simatic_drive_controller_cpu_1507d_tf_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_drive_controller_cpu_1507d_tf >> Version -

Configuraton 0

Siemens>>Simatic_s7-1200_cpu_12_1211c_firmware >> Version To (excluding) 4.5.0

Siemens>>Simatic_s7-1200_cpu_12_1211c >> Version -

Configuraton 0

Siemens>>Simatic_s7-1200_cpu_12_1212c_firmware >> Version To (excluding) 4.5.0

Siemens>>Simatic_s7-1200_cpu_12_1212c >> Version -

Configuraton 0

Siemens>>Simatic_s7-1200_cpu_12_1212fc_firmware >> Version To (excluding) 4.5.0

Siemens>>Simatic_s7-1200_cpu_12_1212fc >> Version -

Configuraton 0

Siemens>>Simatic_s7-1200_cpu_12_1214fc_firmware >> Version To (excluding) 4.5.0

Siemens>>Simatic_s7-1200_cpu_12_1214fc >> Version -

Configuraton 0

Siemens>>Simatic_s7-1200_cpu_12_1214c_firmware >> Version To (excluding) 4.5.0

Siemens>>Simatic_s7-1200_cpu_12_1214c >> Version -

Configuraton 0

Siemens>>Simatic_s7-1200_cpu_12_1215fc_firmware >> Version To (excluding) 4.5.0

Siemens>>Simatic_s7-1200_cpu_12_1215fc >> Version -

Configuraton 0

Siemens>>Simatic_s7-1200_cpu_12_1215c_firmware >> Version To (excluding) 4.5.0

Siemens>>Simatic_s7-1200_cpu_12_1215c >> Version -

Configuraton 0

Siemens>>Simatic_s7-1200_cpu_12_1217c_firmware >> Version To (excluding) 4.5.0

Siemens>>Simatic_s7-1200_cpu_12_1217c >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1510sp-1_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1510sp-1 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1510sp_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1510sp >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1511-1_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1511-1 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_151511c-1_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_151511c-1 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_151511f-1_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_151511f-1 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1511t-1_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1511t-1 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1511tf-1_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1511tf-1 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1512c-1 >> Version -

Siemens>>Simatic_s7-1500_cpu_1512c-1_firmware >> Version To (excluding) 2.9.2

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1512sp-1 >> Version -

Siemens>>Simatic_s7-1500_cpu_1512sp-1_firmware >> Version To (excluding) 2.9.2

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1512spf-1 >> Version -

Siemens>>Simatic_s7-1500_cpu_1512spf-1_firmware >> Version To (excluding) 2.9.2

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1513-1 >> Version -

Siemens>>Simatic_s7-1500_cpu_1513-1_firmware >> Version To (excluding) 2.9.2

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1513f-1 >> Version -

Siemens>>Simatic_s7-1500_cpu_1513f-1_firmware >> Version To (excluding) 2.9.2

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1513r-1 >> Version -

Siemens>>Simatic_s7-1500_cpu_1513r-1_firmware >> Version To (excluding) 2.9.2

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_15prof-2 >> Version -

Siemens>>Simatic_s7-1500_cpu_15prof-2_firmware >> Version To (excluding) 2.9.2

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_15pro-2 >> Version -

Siemens>>Simatic_s7-1500_cpu_15pro-2_firmware >> Version To (excluding) 2.9.2

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1515-2_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1515-2 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1515f-2_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1515f-2 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1515r-2_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1515r-2 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1515t-2_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1515t-2 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1516pro_f_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1516pro_f >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1516-3_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1516-3 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1516f-3_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1516f-3 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1516t-3_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1516t-3 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1516tf-3_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1516tf-3 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1517-3_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1517-3 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1517f-3_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1517f-3 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1518-4_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1518-4 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1518f-4_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1518f-4 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1518hf-4_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1518hf-4 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1518t-4_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1518t-4 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_cpu_1518tf-4_firmware >> Version To (excluding) 2.9.2

Siemens>>Simatic_s7-1500_cpu_1518tf-4 >> Version -

Configuraton 0

Siemens>>Simatic_s7-1500_software_controller >> Version To (excluding) 21.9

Configuraton 0

Siemens>>Simatic_s7-plcsim_advanced_firmware >> Version To (excluding) 4.0

Siemens>>Simatic_s7-plcsim_advanced >> Version -

References