CyberSecBulletin
CVE-2024-52051NVD status: Deferred

A vulnerability has been identified in SIMATIC S7-PLCSIM V17 (All versions), SIMATIC S7-PLCSIM…

Published Updated By the CyberSecBulletin desk

CVE-2024-52051 is a high-severity improper input validation vulnerability in SIMATIC S7-PLCSIM V17 from Siemens, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. Affected SIMATIC S7-PLCSIM V17 versions: all versions. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update SIMATIC STEP 7 Safety V17 to V17 Update 9 or a later version.
  2. Update SIMATIC STEP 7 Safety V18 to V18 Update 6 or a later version.
  3. Update SIMATIC STEP 7 Safety V19 to V19 Update 4 or a later version.
  4. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
SiemensSIMATIC S7-PLCSIM V17all versionsNot stated
SiemensSIMATIC S7-PLCSIM V18all versionsNot stated
SiemensSIMATIC STEP 7 Safety V17before V17 Update 9V17 Update 9
SiemensSIMATIC STEP 7 Safety V18before V18 Update 6V18 Update 6
SiemensSIMATIC STEP 7 Safety V19before V19 Update 4V19 Update 4
SiemensSIMATIC STEP 7 V17before V17 Update 9V17 Update 9
SiemensSIMATIC STEP 7 V18before V18 Update 6V18 Update 6
SiemensSIMATIC STEP 7 V19before V19 Update 4V19 Update 4
SiemensSIMATIC WinCC Unified PC Runtime V18all versionsNot stated
SiemensSIMATIC WinCC Unified PC Runtime V19before V19 Update 4V19 Update 4
SiemensSIMATIC WinCC Unified V17before V17 Update 9V17 Update 9
SiemensSIMATIC WinCC Unified V18before V18 Update 6V18 Update 6
SiemensSIMATIC WinCC Unified V19before V19 Update 4V19 Update 4
SiemensSIMATIC WinCC V17before V17 Update 9V17 Update 9
SiemensSIMATIC WinCC V18before V18 Update 6V18 Update 6
SiemensSIMATIC WinCC V19before V19 Update 4V19 Update 4
SiemensSIMOCODE ES V17all versionsNot stated
SiemensSIMOCODE ES V18all versionsNot stated
SiemensSIMOCODE ES V19all versionsNot stated
SiemensSIMOTION SCOUT TIA V5.4all versionsNot stated
SiemensSIMOTION SCOUT TIA V5.5all versionsNot stated
SiemensSIMOTION SCOUT TIA V5.6before V5.6 SP1 HF7V5.6 SP1 HF7
SiemensSINAMICS Startdrive V17all versionsNot stated
SiemensSINAMICS Startdrive V18all versionsNot stated
SiemensSINAMICS Startdrive V19all versionsNot stated

Version data comes from the organisation that assigned the CVE; 9 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (siemens.com).

Scoring systemScoreSeverityScored by
CVSS 4.07.0HighCNA (siemens.com)
CVSS 3.17.3HighCNA (siemens.com)

Official description

A vulnerability has been identified in SIMATIC S7-PLCSIM V17 (All versions), SIMATIC S7-PLCSIM V18 (All versions), SIMATIC STEP 7 Safety V17 (All versions < V17 Update 9), SIMATIC STEP 7 Safety V18 (All versions < V18 Update 6), SIMATIC STEP 7 Safety V19 (All versions < V19 Update 4), SIMATIC STEP 7 V17 (All versions < V17 Update 9), SIMATIC STEP 7 V18 (All versions < V18 Update 6), SIMATIC STEP 7 V19 (All versions < V19 Update 4), SIMATIC WinCC Unified PC Runtime V18 (All versions), SIMATIC WinCC Unified PC Runtime V19 (All versions < V19 Update 4), SIMATIC WinCC Unified V17 (All versions < V17 Update 9), SIMATIC WinCC Unified V18 (All versions < V18 Update 6), SIMATIC WinCC Unified V19 (All versions < V19 Update 4), SIMATIC WinCC V17 (All versions < V17 Update 9), SIMATIC WinCC V18 (All versions < V18 Update 6), SIMATIC WinCC V19 (All versions < V19 Update 4), SIMOCODE ES V17 (All versions), SIMOCODE ES V18 (All versions), SIMOCODE ES V19 (All versions), SIMOTION SCOUT TIA V5.4 (All versions), SIMOTION SCOUT TIA V5.5 (All versions), SIMOTION SCOUT TIA V5.6 (All versions < V5.6 SP1 HF7), SINAMICS Startdrive V17 (All versions), SINAMICS Startdrive V18 (All versions), SINAMICS Startdrive V19 (All versions), SIRIUS Safety ES V17 (TIA Portal) (All versions), SIRIUS Safety ES V18 (TIA Portal) (All versions), SIRIUS Safety ES V19 (TIA Portal) (All versions), SIRIUS Soft Starter ES V17 (TIA Portal) (All versions), SIRIUS Soft Starter ES V18 (TIA Portal) (All versions), SIRIUS Soft Starter ES V19 (TIA Portal) (All versions), TIA Portal Cloud V17 (All versions), TIA Portal Cloud V18 (All versions), TIA Portal Cloud V19 (All versions < V5.2.1.1). The affected devices do not properly sanitize user-controllable input when parsing user settings. This could allow an attacker to locally execute arbitrary commands in the host operating system with the privileges of the user.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in SIMATIC S7-PLCSIM V17

All SIMATIC S7-PLCSIM V17 vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.