CVE-2025-40771
BaseFortify
Publication date: 2025-10-14
Last updated on: 2025-10-14
Assigner: Siemens AG
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| siemens | siplus_et_200sp_cp_1543sp-1_isec | * |
| siemens | siplus_et_200sp_cp_1542sp-1_irc_tx_rail | * |
| siemens | simatic_cp_1543sp-1 | * |
| siemens | simatic_cp_1542sp-1_irc | * |
| siemens | siplus_et_200sp_cp_1543sp-1_isec_tx_rail | * |
| siemens | simatic_cp_1542sp-1 | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-306 | The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Siemens SIMATIC ET 200SP communication processors, including models CP 1542SP-1, CP 1542SP-1 IRC, CP 1543SP-1, and their SIPLUS variants. The issue is that these devices do not properly authenticate configuration connections, which means an unauthenticated remote attacker could gain access to sensitive configuration data. [1]
How can this vulnerability impact me? :
Because the affected devices do not properly authenticate configuration connections, an unauthenticated remote attacker could access and potentially manipulate sensitive configuration data. This could lead to unauthorized changes in device settings, disruption of industrial network operations, and compromise of the security functions these devices provide, such as firewalls and VPNs. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability involves improper authentication of configuration connections on affected Siemens SIMATIC ET 200SP communication processors. Detection can involve checking the firmware version of the devices to see if they are running a version prior to 2.4.24, which are vulnerable. Siemens does not provide specific detection commands in the provided resources. However, network administrators can identify affected devices by their part numbers and verify firmware versions via device management interfaces or Siemens configuration tools. Monitoring for unauthorized configuration access attempts on these devices may also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating all affected Siemens SIMATIC ET 200SP communication processors to firmware version 2.4.24 or later, which addresses the vulnerability. As an interim measure before updating, restrict access to the affected devices to trusted IP addresses only. Additionally, follow Siemens' general security recommendations such as protecting network access with appropriate security mechanisms and configuring devices according to Siemens' operational guidelines for Industrial Security. [1]