CVE-2019-10917
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 · uneditedA vulnerability has been identified in SIMATIC PCS 7 V8.0 and earlier (All versions), SIMATIC PCS 7 V8.1 (All versions < V8.1 with WinCC V7.3 Upd 19), SIMATIC PCS 7 V8.2 (All versions < V8.2 SP1 with WinCC V7.4 SP1 Upd11), SIMATIC PCS 7 V9.0 (All versions < V9.0 SP2 with WinCC V7.4 SP1 Upd11), SIMATIC WinCC (TIA Portal) V13 (All versions), SIMATIC WinCC (TIA Portal) V14 (All versions < V14 SP1 Upd 9), SIMATIC WinCC (TIA Portal) V15 (All versions < V15.1 Upd 3), SIMATIC WinCC Runtime Professional V13 (All versions), SIMATIC WinCC Runtime Professional V14 (All versions < V14.1 Upd 8), SIMATIC WinCC Runtime Professional V15 (All versions < V15.1 Upd 3), SIMATIC WinCC V7.2 and earlier (All versions), SIMATIC WinCC V7.3 (All versions < V7.3 Upd 19), SIMATIC WinCC V7.4 (All versions < V7.4 SP1 Upd 11), SIMATIC WinCC V7.5 (All versions < V7.5 Upd 3). An attacker with local access to the project file could cause a Denial-of-Service condition on the affected product while the project file is loaded. Successful exploitation requires access to the project file. An attacker could use the vulnerability to compromise availability of the affected system. At the time of advisory publication no public exploitation of this security 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 confidenceA parsing vulnerability exists in multiple SIMATIC WinCC and PCS 7 versions where a specially crafted project file, when loaded by an authorized user, causes a denial-of-service condition. The attacker requires local access to the project file but does not need authentication—the vulnerability is triggered during file processing.
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<= 8.0= 8.1= 8.2= 9.0<= 7.2= 7.3= 7.4= 7.5= 13.0= 14.0= 15.0all versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Simatic WinCC versionOpen the Windows Programs and Features control panel, or check the installation directory for the WinCC version file (typically in C:\Program Files\Siemens\WinCC\). You can also run 'winccver.exe' if present in the WinCC bin folder.Affected if The installed version is WinCC <= 7.2, = 7.3, = 7.4, = 7.5, or WinCC Runtime Professional of any version (all affected).
-
Identify installed Simatic PCS 7 versionCheck the SIMATIC Manager or the PCS 7 project properties. The version is typically visible in the project information dialog or in the Windows Programs and Features list.Affected if The installed version is PCS 7 <= 8.0, = 8.1, = 8.2, or = 9.0.
-
Identify installed Simatic WinCC TIA Portal versionOpen the TIA Portal launcher and check the software version displayed, or look in the Windows Programs and Features list for 'Siemens Totally Integrated Automation Portal V' followed by the version number.Affected if The installed version is TIA Portal = 13.0, = 14.0, or = 15.0.
-
Locate WinCC or PCS 7 project filesSearch the file system for project file extensions used by WinCC and PCS 7, such as .apj, .wcp, .wcf, or project folders under typical installation paths like C:\Projects\Simatic\WinCC or C:\Projects\Simatic\PCS7.Affected if Project files exist on the system, these are the files that could be replaced with a specially crafted malicious file to trigger the vulnerability.
-
Verify local user access to project filesCheck file system permissions on identified project directories. Determine if untrusted local users have read or write access to these locations, or if multiple users share the same system.Affected if Multiple users have access to the same system and can place files in project directories, or a local attacker could replace legitimate project files with a malicious one.
Your environment is affected if any installed version of WinCC, WinCC Runtime Professional, WinCC TIA Portal, or PCS 7 matches the affected version ranges AND project files exist on the system that could be replaced by a maliciously crafted file.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied updates: WinCC V7.2 and earlier require upgrade; V7.3 needs Update 19, V7.4 needs SP1 Update 11, V7.5 needs Update 3; TIA Portal V14 needs SP1 Update 9, V15 needs Update 3. Restrict local access to project files until patches are applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10917 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10917 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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