Simatic Process Control System NeoApplication · Siemens

CVE-2020-25238

HIGH · 7.8 CVSS v3.1 Published 2021-02-09
Fix available
A fix is available. Upgrade to 3.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 PCS neo (Administration Console) (All versions < V3.1), TIA Portal (V15, V15.1 and V16). Manipulating certain files in specific folders could allow a local attacker to execute code with SYSTEM privileges. The security vulnerability could be exploited by an attacker with a valid account and limited access rights on the system.

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

This is a local privilege escalation vulnerability in Siemens TIA Portal (V15, V15.1, V16) and PCS neo Administration Console (all versions < V3.1). An attacker with a valid low-privileged user account can manipulate certain files in specific folders to achieve arbitrary code execution with SYSTEM privileges.

MitigationApply vendor updates: upgrade PCS neo Administration Console to V3.1 or later; apply available patches for affected TIA Portal versions. Until patched, restrict file system permissions on vulnerable folders and minimize the number of users with local system access.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Simatic Process Control System NeoApplication
Affected:< 3.1
Totally Integrated Automation PortalApplication
Affected:= 15= 15.1= 16

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 TIA Portal version
    Check the Windows Programs and Features list or look for Siemens TIA Portal entries in the installation directory for version numbers (V15, V15.1, or V16)
    Affected if TIA Portal versions 15, 15.1, or 16 are installed
  2. Identify installed PCS neo Administration Console version
    Check Windows Programs and Features for Siemens PCS neo Administration Console and note the installed version
    Affected if PCS neo Administration Console version is earlier than V3.1 or the version cannot be confirmed as V3.1 or later
  3. Verify low-privileged user accounts exist
    Review local user accounts or domain users who have access to the system with standard user privileges (not administrators)
    Affected if Low-privileged user accounts with file system access exist on the affected system
  4. Confirm presence of vulnerable folder permissions
    Inspect file system permissions on TIA Portal or PCS neo installation directories where user-writable folders exist that could be manipulated
    Affected if Low-privileged users have write permissions to critical application folders that should be restricted to administrators only
  5. Check for recent privilege escalation indicators
    Review Windows event logs for unexpected processes spawning under the SYSTEM account, particularly from paths associated with TIA Portal or PCS neo installations
    Affected if Evidence exists of code execution under SYSTEM privileges originating from user-accessible application paths

You are affected if either Siemens TIA Portal V15, V15.1, or V16 OR PCS neo Administration Console versions before V3.1 are installed AND low-privileged users have write access to application directories.

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.

From vendor data
Upgrade available Upgrade to 3.1 or later
Fixed in 3.1
Interim mitigation

Apply vendor updates: upgrade PCS neo Administration Console to V3.1 or later; apply available patches for affected TIA Portal versions. Until patched, restrict file system permissions on vulnerable folders and minimize the number of users with local system access.

Fix this in Simatic Process Control System Neo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2020-25238 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