dbcve.org
Simatic Pcs 7Application · Siemens

CVE-2022-24287

HIGH · 7.8 CVSS v3.1 Published 2022-05-20
Fix available
A fix is available. Upgrade to after 16 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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 PCS 7 V8.2 (All versions), SIMATIC PCS 7 V9.0 (All versions < V9.0 SP3 UC06), SIMATIC PCS 7 V9.1 (All versions < V9.1 SP1 UC01), SIMATIC WinCC Runtime Professional V16 and earlier (All versions), SIMATIC WinCC Runtime Professional V17 (All versions < V17 Upd4), SIMATIC WinCC V7.3 (All versions), SIMATIC WinCC V7.4 (All versions < V7.4 SP1 Update 21), SIMATIC WinCC V7.5 (All versions < V7.5 SP2 Update 8). A missing printer configuration on the host could allow an authenticated attacker to escape the WinCC Kiosk Mode.

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

A detailed technical summary for this CVE is being prepared.

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 Pcs 7Application
Affected:<= 9.0= 9.1
Simatic WinccApplication
Affected:<= 7.4= 7.5
Simatic Wincc Runtime ProfessionalApplication
Affected:<= 16= 17

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

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
Upgrade available Upgrade to a release after 16
Vendor patch cert-portal.siemens.com →
Recommended fix High confidence

SIMATIC PCS 7 V9.0 -> V9.0 SP3 UC06; SIMATIC PCS 7 V9.1 -> V9.1 SP1 UC01; WinCC V7.4 -> V7.4 SP1 Update 21; WinCC V7.5 -> V7.5 SP2 Update 8; WinCC Runtime V17 -> V17 Update 4

  1. For SIMATIC PCS 7 V9.0: Upgrade to V9.0 SP3 UC06 or later
  2. For SIMATIC PCS 7 V9.1: Upgrade to V9.1 SP1 UC01 or later
  3. For SIMATIC WinCC V7.4: Upgrade to V7.4 SP1 Update 21 or later
  4. For SIMATIC WinCC V7.5: Upgrade to V7.5 SP2 Update 8 or later
  5. For SIMATIC WinCC Runtime Professional V16 and earlier: Upgrade to V17 Update 4 or later
  6. For SIMATIC WinCC Runtime Professional V17: Upgrade to V17 Update 4 or later
  7. Apply the vendor patch from https://cert-portal.siemens.com/productcert/pdf/ssa-363107.pdf after upgrading
  8. Verify the kiosk mode properly restricts access after patching
Caveat Review Siemens patch notes for compatibility with other SIMATIC software in your environment before upgrading

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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