CVE-2025-40566

8.8 HIGH

📋 TL;DR

This vulnerability allows session hijacking in Siemens SIMATIC PCS neo industrial control systems. An attacker who obtains a valid session token can reuse it even after the legitimate user logs out, potentially gaining unauthorized access. Affected systems include SIMATIC PCS neo V4.1 (before Update 3) and V5.0 (before Update 1).

💻 Affected Systems

Products:
  • SIMATIC PCS neo
Versions: V4.1 (All versions < V4.1 Update 3), V5.0 (All versions < V5.0 Update 1)
Operating Systems: Not specified in CVE, typically runs on Windows-based industrial systems
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of specified versions; no special configuration required for vulnerability.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker gains persistent administrative access to industrial control systems, enabling sabotage, data theft, or disruption of critical industrial processes.

🟠

Likely Case

Unauthorized access to operator interfaces allowing configuration changes, process monitoring, or data exfiltration from industrial networks.

🟢

If Mitigated

Limited impact due to network segmentation, strong authentication controls, and session monitoring preventing token capture.

🌐 Internet-Facing: HIGH if systems are exposed to internet, as unauthenticated attackers could exploit captured tokens remotely.
🏢 Internal Only: MEDIUM as attackers would need internal network access first, but session reuse remains possible once tokens are obtained.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires obtaining session tokens through other means (network sniffing, XSS, etc.), but actual session reuse is straightforward once tokens are acquired.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: V4.1 Update 3 or V5.0 Update 1

Vendor Advisory: https://cert-portal.siemens.com/productcert/html/ssa-339086.html

Restart Required: Yes

Instructions:

1. Download appropriate update from Siemens support portal. 2. Backup system configuration. 3. Apply V4.1 Update 3 for V4.1 systems or V5.0 Update 1 for V5.0 systems. 4. Restart affected systems. 5. Verify session invalidation works correctly.

🔧 Temporary Workarounds

Session Timeout Reduction

all

Reduce session timeout values to limit window for token reuse

Configure via SIMATIC PCS neo administration interface: Set session timeout to minimum practical value

Network Segmentation

all

Isolate SIMATIC PCS neo systems from untrusted networks

Implement firewall rules to restrict access to trusted IPs only

🧯 If You Can't Patch

  • Implement strict network segmentation to prevent unauthorized access to SIMATIC PCS neo systems
  • Deploy session monitoring and alerting for suspicious session reuse patterns

🔍 How to Verify

Check if Vulnerable:

Check SIMATIC PCS neo version in administration interface; if V4.1 < Update 3 or V5.0 < Update 1, system is vulnerable.

Check Version:

Check via SIMATIC PCS neo administration panel or Siemens diagnostic tools

Verify Fix Applied:

After patching, test session invalidation: 1. Log in as user. 2. Capture session token. 3. Log out. 4. Attempt to reuse token - should be rejected.

📡 Detection & Monitoring

Log Indicators:

  • Multiple successful logins from same session ID after logout events
  • Session IDs being used from unexpected IP addresses

Network Indicators:

  • Unauthorized API calls using previously valid session tokens
  • Traffic patterns suggesting session reuse

SIEM Query:

source="simatic_logs" AND (event_type="session_reuse" OR (auth_success AND session_id IN (SELECT session_id FROM logs WHERE event_type="logout")))

🔗 References

📤 Share & Export