CyberzSOC

Publication detail
← Back to advisories & guidance

ICSA-25-261-03: Schneider Electric Saitel DR & Saitel DP Remote Terminal Unit ↗ source

September 18, 2025 CISA ICS Advisory

Summary

Successful exploitation of these vulnerabilities could enable an attacker to execute arbitrary shell commands on the affected devices. CVE-2025-9996: A OS command injection vulnerability exists that could cause the execution of any shell command when executing a netstat command using BLMon Console in anSSH session. CVE-2025-9997: CWE-78: Improper Neutralization of Special Elements used in an OS Command vulnerability exists that couldcause command injection in BLMon that is executed in the operating system console when in a SSH session.

Advisory Details CISA ICS CSAF feed

Advisory ID
ICSA-25-261-03
Status
Final · version 1
Initial release
2025-09-18
Last revised
2025-09-18
Vendor
Schneider Electric
Critical infrastructure sectors
Commercial Facilities, Critical Manufacturing, Energy
Deployed
Worldwide
Vendor headquarters
France

No known public exploitation specifically targeting these vulnerabilities has been reported to CISA at this time. These vulnerabilities are not exploitable remotely.

Credit: Robin Senn (GAI NetConsult GmbH); Sebastian Krause (GAI NetConsult GmbH)

Affected products (2)
  • Schneider Electric Saitel DR RTU — <=11.06.29
  • Schneider Electric Saitel DP RTU — <=11.06.33

From CISA's machine-readable CSAF 2.0 advisory (JSON).

Vulnerabilities as Stated by the Advisory

CVEWeaknessCVSS v3Details
CVE-2025-9996 CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') 6.6 Medium A OS command injection vulnerability exists that could cause the execution of any shell command when executing a netstat command using BLMon Console in anSSH session.

Mitigation: Schneider Electric has identified the following specific workarounds and mitigations users can apply to reduce risk:

Vendor fix: Schneider Electric Saitel DR RTU Versions 11.06.29 and prior: HUe Firmware version 11.06.30 of Saitel DR includes a fix for this vulnerability and is available for download. A reboot is necessary to complete the firmware upgrade. ↗

Vendor fix: Schneider Electric Saitel DP RTU Versions 11.06.33 and prior: Firmware SM_CPU866e version 11.06.34 of Saitel DP includes a fix for this vulnerability and is available for download. A reboot is necessary to complete the firmware upgrade. ↗

Affected, fixed & timeline

Affected:

  • Schneider Electric Saitel DR RTU <=11.06.29
  • Schneider Electric Saitel DP RTU <=11.06.33

Mitigation: Schneider Electric recommends that customers use appropriate patching methodologies when applying these patches to their systems. They strongly recommend the use of back-ups and evaluating the impact of these patches in a Test and Development environment or on an offline infrastructure. Contact Schneider Electric's Customer Care Center for assistance removing a patch.

Mitigation: If customers are not able to apply these patches, Schneider Electric recommends immediately applying the following mitigations to reduce the risk of exploitation:

Mitigation: Restrict access to BLMon by assigning permissions only to a limited set of user roles.

Mitigation: Ensure users are assigned the least privileged role that still allows them to perform their designated tasks.

Mitigation: Implement firewall rules to restrict SSH connections to the device.

Mitigation: Schneider Electric strongly recommends the following industry cybersecurity best practices.

Mitigation: Locate control and safety system networks and remote devices behind firewalls and isolate them from the business network.

Mitigation: Install physical controls so no unauthorized personnel can access your industrial control and safety systems, components, peripheral equipment, and networks.

Mitigation: Place all controllers in locked cabinets and never leave them in the "Program" mode.

Mitigation: Never connect programming software to any network other than the network intended for that device.

Mitigation: Scan all methods of mobile data exchange with the isolated network such as CDs, USB drives, etc. before use in the terminals or any node connected to these networks.

Mitigation: Never allow mobile devices that have connected to any other network besides the intended network to connect to the safety or control networks without proper sanitation.

Mitigation: Minimize network exposure for all control system devices and systems and ensure that they are not accessible from the Internet.

Mitigation: When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.

Mitigation: For more information refer to the Schneider Electric Recommended Cybersecurity Best Practices document.

Mitigation: For more information see the associated Schneider Electric CPCERT security advisory SEVD-2025-252-02 Saitel DR & Saitel DP Remote Terminal Unit - SEVD-2025-252-02 PDF Version, Saitel DR & Saitel DP Remote Terminal Unit - SEVD-2025-252-02 CSAF Version.

Mitigation: For more information see the associated Schneider Electric CPCERT security advisory SEVD-2025-252-02 Saitel DR & Saitel DP Remote Terminal Unit - SEVD-2025-252-02 PDF Version, Saitel DR & Saitel DP Remote Terminal Unit - SEVD-2025-252-02 CSAF Version.

CVE-2025-9997 CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') 6.6 Medium CWE-78: Improper Neutralization of Special Elements used in an OS Command vulnerability exists that couldcause command injection in BLMon that is executed in the operating system console when in a SSH session.

Mitigation: Schneider Electric has identified the following specific workarounds and mitigations users can apply to reduce risk:

Vendor fix: Schneider Electric Saitel DR RTU Versions 11.06.29 and prior: HUe Firmware version 11.06.30 of Saitel DR includes a fix for this vulnerability and is available for download. A reboot is necessary to complete the firmware upgrade. ↗

Vendor fix: Schneider Electric Saitel DP RTU Versions 11.06.33 and prior: Firmware SM_CPU866e version 11.06.34 of Saitel DP includes a fix for this vulnerability and is available for download. A reboot is necessary to complete the firmware upgrade. ↗

Affected, fixed & timeline

Affected:

  • Schneider Electric Saitel DR RTU <=11.06.29
  • Schneider Electric Saitel DP RTU <=11.06.33

Mitigation: Schneider Electric recommends that customers use appropriate patching methodologies when applying these patches to their systems. They strongly recommend the use of back-ups and evaluating the impact of these patches in a Test and Development environment or on an offline infrastructure. Contact Schneider Electric's Customer Care Center for assistance removing a patch.

Mitigation: If customers are not able to apply these patches, Schneider Electric recommends immediately applying the following mitigations to reduce the risk of exploitation:

Mitigation: Restrict access to BLMon by assigning permissions only to a limited set of user roles.

Mitigation: Ensure users are assigned the least privileged role that still allows them to perform their designated tasks.

Mitigation: Implement firewall rules to restrict SSH connections to the device.

Mitigation: Schneider Electric strongly recommends the following industry cybersecurity best practices.

Mitigation: Locate control and safety system networks and remote devices behind firewalls and isolate them from the business network.

Mitigation: Install physical controls so no unauthorized personnel can access your industrial control and safety systems, components, peripheral equipment, and networks.

Mitigation: Place all controllers in locked cabinets and never leave them in the "Program" mode.

Mitigation: Never connect programming software to any network other than the network intended for that device.

Mitigation: Scan all methods of mobile data exchange with the isolated network such as CDs, USB drives, etc. before use in the terminals or any node connected to these networks.

Mitigation: Never allow mobile devices that have connected to any other network besides the intended network to connect to the safety or control networks without proper sanitation.

Mitigation: Minimize network exposure for all control system devices and systems and ensure that they are not accessible from the Internet.

Mitigation: When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.

Mitigation: For more information refer to the Schneider Electric Recommended Cybersecurity Best Practices document.

Mitigation: For more information see the associated Schneider Electric CPCERT security advisory SEVD-2025-252-02 Saitel DR & Saitel DP Remote Terminal Unit - SEVD-2025-252-02 PDF Version, Saitel DR & Saitel DP Remote Terminal Unit - SEVD-2025-252-02 CSAF Version.

Mitigation: For more information see the associated Schneider Electric CPCERT security advisory SEVD-2025-252-02 Saitel DR & Saitel DP Remote Terminal Unit - SEVD-2025-252-02 PDF Version, Saitel DR & Saitel DP Remote Terminal Unit - SEVD-2025-252-02 CSAF Version.

Scores and weakness types are as CISA or the republishing vendor stated them in this advisory; the linked CVE pages carry the independently enriched CVSS and SSVC assessments.

News Coverage

No coverage found in monitored research blogs or news feeds.

CVEs Referenced in This Publication

CVECVSSAffected
CVE-2025-9996 5.8 Medium Schneider Electric Saitel DR RTU CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability exists that could cause the executio…
CVE-2025-9997 5.8 Medium Schneider Electric Saitel DR RTU CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability exists that could cause command inje…

Named by the advisory itself. Each CVE links to its tracked detail page.

Vendors Named in This Publication

Each vendor links to its Known Exploited Vulnerabilities catalog page. Only vendors that appear in the KEV catalog are listed, either because the publication cites one of their KEV entries or because it names them directly.