dbcve.org
Openpcs 7Application · Siemens

CVE-2023-48364

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to after 18 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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 OpenPCS 7 V9.1 (All versions < V9.1 SP2 UC05), SIMATIC BATCH V9.1 (All versions < V9.1 SP2 UC05), SIMATIC PCS 7 V9.1 (All versions < V9.1 SP2 UC05), SIMATIC Route Control V9.1 (All versions < V9.1 SP2 UC05), SIMATIC WinCC Runtime Professional V18 (All versions < V18 Update 4), SIMATIC WinCC Runtime Professional V19 (All versions < V19 Update 2), SIMATIC WinCC V7.4 (All versions), SIMATIC WinCC V7.5 (All versions < V7.5 SP2 Update 15), SIMATIC WinCC V8.0 (All versions < V8.0 Update 4). The implementation of the RPC (Remote Procedure call) communication protocol in the affected products do not properly handle certain malformed RPC messages. An attacker could use this vulnerability to cause a denial of service condition in the RPC server.

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

The vulnerability exists in the RPC (Remote Procedure Call) protocol implementation across multiple Siemens SIMATIC WinCC and PCS 7 products. The improper handling of malformed RPC messages allows an attacker to crash the RPC server, causing denial of service. Affected products include SIMATIC WinCC V7.4, V7.5, V8.0, V18, V19 and PCS 7 V9.1 variants.

MitigationUpgrade to vendor-supplied patched versions: V9.1 SP2 UC05 for PCS 7 products, Update 4 for WinCC V18, Update 2 for WinCC V19, Update 15 for WinCC V7.5 SP2, and Update 4 for WinCC V8.0. WinCC V7.4 has no fix indicated.

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
Openpcs 7Application
Affected:<= 9.1
Simatic BatchApplication
Affected:<= 9.1
Simatic Pcs 7Application
Affected:<= 9.1
Simatic Route ControlApplication
Affected:<= 9.1
Simatic WinccApplication
Affected:= 7.4= 7.5= 8.0
Simatic Wincc Runtime ProfessionalApplication
Affected:<= 18= 19

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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 checks

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

  1. Identify installed Siemens product
    Check Programs and Features or registry for Siemens SIMATIC WinCC, PCS 7, Simatic Batch, Simatic Route Control, or OpenPCS 7 installations. Note the exact product name and version listed.
    Affected if Product name matches any of the affected products (WinCC, PCS 7, Simatic Batch, Simatic Route Control, OpenPCS 7) and version falls within affected ranges.
  2. Verify installed version number
    Locate the specific version number in the Windows installed programs list, or check Siemens-specific registry keys under HKLM\SOFTWARE\Siemens\ for the installed product version.
    Affected if Version is WinCC 7.4, 7.5, or 8.0; WinCC Runtime Professional <=18 or =19; PCS 7, Simatic Batch, Simatic Route Control, or OpenPCS 7 <=9.1.
  3. Confirm RPC server component is active
    Check if the RPC service or specific WinCC/PCS 7 RPC services are running. Look for services named 'SIMATIC WinCC' or 'RPC' in Windows Services, or check if port 135 (DCOM RPC) is listening.
    Affected if RPC server services are enabled and running, making the vulnerability exploitable.

User is affected if they have any of the listed Siemens products installed with a version matching the affected ranges AND the RPC server component is active.

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
Upgrade available Upgrade to a release after 18
Interim mitigation

Upgrade to vendor-supplied patched versions: V9.1 SP2 UC05 for PCS 7 products, Update 4 for WinCC V18, Update 2 for WinCC V19, Update 15 for WinCC V7.5 SP2, and Update 4 for WinCC V8.0. WinCC V7.4 has no fix indicated.

Recommended fix High confidence

Product-specific: V9.1 SP2 UC05 (OpenPCS/Batch/PCS7/Route Control), V7.5 SP2 Update 15 (WinCC V7.5), V8.0 Update 4 (WinCC V8.0), V18 Update 4 (WinCC Runtime V18), V19 Update 2 (WinCC Runtime V19)

  1. 1. Identify the specific Siemens SIMATIC product and version running in your environment from the affected list (OpenPCS 7, SIMATIC BATCH, SIMATIC PCS 7, SIMATIC Route Control, SIMATIC WinCC, or SIMATIC WinCC Runtime Professional).
  2. 2. For OpenPCS 7 V9.1, SIMATIC BATCH V9.1, SIMATIC PCS 7 V9.1, and SIMATIC Route Control V9.1: upgrade to version V9.1 SP2 UC05 or later.
  3. 3. For SIMATIC WinCC V7.5: upgrade to V7.5 SP2 Update 15 or later.
  4. 4. For SIMATIC WinCC V8.0: upgrade to V8.0 Update 4 or later.
  5. 5. For SIMATIC WinCC Runtime Professional V18: upgrade to V18 Update 4 or later.
  6. 6. For SIMATIC WinCC Runtime Professional V19: upgrade to V19 Update 2 or later.
  7. 7. After upgrading, verify the RPC service is functioning correctly and monitor for any issues.
  8. 8. For SIMATIC WinCC V7.4: contact Siemens directly for guidance as no fixed version is specified in the advisory.
Caveat Upgrades between major versions or to service packs may require testing; consult Siemens release notes for compatibility and migration guidance

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

Fix this in Openpcs 7 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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