Simatic Step 7 \(tia Portal\)Application · Siemens

CVE-2018-13811

MEDIUM · 5.5 CVSS v3.0 Published 2018-12-13
Fix available
A fix is available. Upgrade to 15.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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 SIMATIC STEP 7 (TIA Portal) (All Versions < V15.1). Password hashes with insufficient computational effort could allow an attacker to access to a project file and reconstruct passwords. The vulnerability could be exploited by an attacker with local access to the project file. No user interaction is required to exploit the vulnerability. The vulnerability could allow the attacker to obtain certain passwords from the project. At the time of advisory publication no public exploitation of this vulnerability was known.

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

SIMATIC STEP 7 (TIA Portal) versions prior to V15.1 use password hashing with insufficient computational effort (likely weak or uniterated algorithms). An attacker with local access to a project file can extract these weak password hashes and perform offline cracking to recover plaintext passwords.

MitigationUpgrade to SIMATIC STEP 7 (TIA Portal) V15.1 or later which implements proper password hashing. Additionally, restrict physical and file-system access to project files to limit exposure.

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 Step 7 \(tia Portal\)Application
Affected:< 15.1

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
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 SIMATIC STEP 7 (TIA Portal) version
    Open the TIA Portal application and navigate to Help > About, or check the installed programs list in Windows Control Panel for the version number
    Affected if The version displayed is earlier than V15.1 (e.g., V14, V13, V12, etc.)
  2. Locate TIA Portal project files on the system
    Search for project directories on local drives or network shares, typically stored with extensions such as .ap15, .ap14, or similar project file formats used by TIA Portal
    Affected if Project files exist and the TIA Portal version is before V15.1
  3. Identify if project files contain password-protected elements
    Open project files using TIA Portal and examine the project tree for password-protected blocks, programs, or access protection settings. Check for any password configuration in the project properties
    Affected if Any password protection is configured in the project and the TIA Portal version is before V15.1
  4. Assess local access exposure to project files
    Review file system permissions on project directories to determine if unauthorized local users could read project files
    Affected if Project files with passwords are accessible to users beyond the intended authorized users and TIA Portal version is before V15.1

The environment is affected if SIMATIC STEP 7 (TIA Portal) version is earlier than V15.1 AND project files with password protection exist on the system.

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 15.1 or later
Fixed in 15.1
Interim mitigation

Upgrade to SIMATIC STEP 7 (TIA Portal) V15.1 or later which implements proper password hashing. Additionally, restrict physical and file-system access to project files to limit exposure.

Fix this in Simatic Step 7 \(tia Portal\) Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-13811 — 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-2018-13811 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