Siemens SIDIS Secured SmartPlug Vulnerabilities
CISA has identified multiple vulnerabilities in Siemens SIDIS Secured SmartPlug, including improper enforcement of message integrity, reuse of nonces, and out-of-bounds writes. Siemens recommends updating to the latest version, V7.26.0310 or later.
Intelligence analysis by Llama
CISA has identified multiple vulnerabilities in Siemens SIDIS Secured SmartPlug, including improper enforcement of message integrity, reuse of nonces, and out-of-bounds writes. Siemens recommends updating to the latest version, V7.26.0310 or later. The vulnerabilities affect various components, including OpenSSL, OpenSSH, and several other packages.
Imagine you have a smart plug that controls your home appliances. But, what if someone could hack into the plug and turn off your lights or even your entire house? That's what's happening with the Siemens SIDIS Secured SmartPlug. There are some bugs in the plug's code that could let hackers take control. To fix this, Siemens is releasing a new version of the plug that fixes these bugs. It's like updating your phone's operating system to fix security issues.
Analysis
Vulnerabilities Overview
CISA has identified multiple vulnerabilities in Siemens SIDIS Secured SmartPlug, including improper enforcement of message integrity, reuse of nonces, and out-of-bounds writes. These vulnerabilities affect various components, including OpenSSL, OpenSSH, and several other packages.
CVE-2022-23303: Side Channel Attacks
The implementations of SAE in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side channel attacks as a result of cache access patterns. This issue exists because of an incomplete fix for CVE-2019-9494.
CVE-2022-23304: Side-Channel Attacks
The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of cache access patterns. This issue exists because of an incomplete fix for CVE-2019-9495.
CVE-2022-37660: PKEX Association
In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public keys with another entity using PKEX in the past, will be able to subvert a future bootstrapping by passively observing public keys, re-using the encrypting element Qi and subtracting it from the captured message M (X = M - Qi). This will result in the public ephemeral key X; the only element required to subvert the PKEX association.
CVE-2022-48174: Stack Overflow Vulnerability
There is a stack overflow vulnerability in ash.c:6030 in busybox before 1.35. In the environment of Internet of Vehicles, this vulnerability can be executed from command to arbitrary code execution.
CVE-2025-5222: Stack Buffer Overflow
A stack buffer overflow was found in Internationl components for unicode (ICU ). While running the genrb binary, the 'subtag' struct overflowed at the SRBRoot::addTag function. This issue may lead to memory corruption and local arbitrary code execution.
CVE-2025-5914: Integer Overflow
A vulnerability has been identified in the libarchive library, specifically within the archive_read_format_rar_seek_data() function. This flaw involves an integer overflow that can ultimately lead to a double-free condition. Exploiting a double-free vulnerability can result in memory corruption, enabling an attacker to execute arbitrary code or cause a denial-of-service condition.
Key points
- Multiple vulnerabilities identified in Siemens SIDIS Secured SmartPlug
- Improper enforcement of message integrity, reuse of nonces, and out-of-bounds writes
- Siemens recommends updating to the latest version, V7.26.0310 or later
- Vulnerabilities affect various components, including OpenSSL, OpenSSH, and several other packages
If Siemens updates the SIDIS Secured SmartPlug to the latest version, it will fix the identified vulnerabilities and ensure the security and integrity of the system. This will prevent potential attacks and protect critical infrastructure sectors.
If the vulnerabilities in the SIDIS Secured SmartPlug are not addressed, it could lead to significant risks to critical infrastructure sectors, including critical manufacturing. This could result in data breaches, system crashes, or even physical damage to equipment.



