dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-52051

HIGH · 7.3 CVSS v3.1 Published 2024-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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), 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), 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), SIMATIC WinCC Unified V19 (All versions < V19 Update 4), SIMATIC WinCC V17 (All versions < V17 Update 9), SIMATIC WinCC V18 (All versions), 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in multiple Siemens TIA Portal and related industrial software products. The affected devices do not properly sanitize user-controllable input when parsing user settings, allowing a local attacker to execute arbitrary commands on the host operating system with the privileges of the current user.

MitigationApply vendor-supplied updates: STEP 7 V17 Update 9, V19 Update 4; WinCC V17 Update 9, V19 Update 4; WinCC Unified V17 Update 9, V19 Update 4; SIMOTION SCOUT TIA V5.6 SP1 HF7; TIA Portal Cloud V5.2.1.1; and corresponding updates for PLCSIM, Safety, SIMOCODE ES, SINAMICS Startdrive, SIRIUS Safety ES, and SIRIUS Soft Starter ES as specified in the advisory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Siemens TIA Portal software
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -match 'TIA Portal|STEP 7|WinCC|SIMOTION|SINAMICS|SIMOCODE|SIRIUS'}. Check Program Files\Siemens for TIA Portal installation folders.
    Affected if Any TIA Portal, STEP 7, WinCC, SIMOTION SCOUT TIA, or related Siemens industrial software is installed.
  2. Determine exact version of TIA Portal components
    In the installed software list, note the version displayed (such as V17, V19, V5.6 SP1, V5.2). Also check within the TIA Portal application: Open TIA Portal > Help > About, or check the installation directory for version info files.
    Affected if Version is V17, V19, V5.6 SP1, or V5.2.
  3. Check if version is before patched release
    For V17: confirm if Update 9 is applied (look for version like V17 Update 9 or higher). For V19: confirm if Update 4 is applied. For V5.6 SP1: confirm if HF7 is applied. For V5.2: confirm if version is higher than 5.2.1.1. Compare your version against these minimum fixed versions.
    Affected if Running V17 before Update 9, V19 before Update 4, V5.6 SP1 before HF7, or V5.2 before 5.2.1.1.
  4. Verify the user settings parsing feature is in use
    This vulnerability affects parsing of user settings. Check if the software has been used to create or modify projects, or if user configuration files exist in the user profile or project directories under %APPDATA%\Siemens or within project folders.
    Affected if The software has been used to load or parse user settings or project files, which triggers the vulnerable parsing code path.

You are affected if you have installed any version of Siemens TIA Portal, STEP 7, WinCC, or related industrial software that is V17 before Update 9, V19 before Update 4, V5.6 SP1 before HF7, or V5.2 before 5.2.1.1, and the software parses user-controllable settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied updates: STEP 7 V17 Update 9, V19 Update 4; WinCC V17 Update 9, V19 Update 4; WinCC Unified V17 Update 9, V19 Update 4; SIMOTION SCOUT TIA V5.6 SP1 HF7; TIA Portal Cloud V5.2.1.1; and corresponding updates for PLCSIM, Safety, SIMOCODE ES, SINAMICS Startdrive, SIRIUS Safety ES, and SIRIUS Soft Starter ES as specified in the advisory.

Recommended fix Moderate confidence

Upgrade to the specific Update versions mentioned (V17 Update 9, V19 Update 4, V5.6 SP1 HF7, TIA Portal Cloud V5.2.1.1) or contact Siemens for available patches for versions without listed fixes

  1. 1. Identify the exact installed version of the affected Siemens software (TIA Portal, STEP 7, WinCC, SIMATIC S7-PLCSIM, SIMOCODE ES, SIMOTION SCOUT TIA, SINAMICS Startdrive, SIRIUS Safety ES, SIRIUS Soft Starter ES).
  2. 2. For SIMATIC STEP 7 V17: upgrade to V17 Update 9 or later.
  3. 3. For SIMATIC STEP 7 V19: upgrade to V19 Update 4 or later.
  4. 4. For SIMATIC STEP 7 Safety V17: upgrade to V17 Update 9 or later.
  5. 5. For SIMATIC STEP 7 Safety V19: upgrade to V19 Update 4 or later.
  6. 6. For SIMATIC WinCC V17: upgrade to V17 Update 9 or later.
  7. 7. For SIMATIC WinCC V19: upgrade to V19 Update 4 or later.
  8. 8. For SIMATIC WinCC Unified V17: upgrade to V17 Update 9 or later.
Caveat Upgrading major software versions may require project migration; test thoroughly in a non-production environment before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA4.0 h
34.0 hours of engineering $5,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52051 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data