dbcve.org
Openpcs 7Application · Siemens

CVE-2023-48363

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 unorganized 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 RPC (Remote Procedure Call) protocol implementation in multiple Siemens SIMATIC industrial automation products fails to properly handle certain malformed or unorganized RPC messages. An attacker sending specially crafted RPC messages can cause the RPC server to crash, resulting in denial of service.

MitigationApply vendor patches: upgrade to V9.1 SP2 UC05 or later for V9.1 products, V18 Update 4/V19 Update 2 for WinCC Runtime Professional, V7.5 SP2 Update 15 for WinCC V7.5, V8.0 Update 4 for WinCC V8.0; WinCC V7.4 has no patch available per advisory - contact vendor for mitigations.

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 SIMATIC product
    Check the Windows Programs and Features list or the product's About dialog for the exact product name (Openpcs 7, Simatic Batch, Simatic Pcs 7, Simatic Route Control, Simatic Wincc, or Simatic Wincc Runtime Professional)
    Affected if The installed product matches one of the affected products listed in the CVE advisory
  2. Determine the installed version number
    Open the product's main application, navigate to Help > About or the system information panel, and record the full version string including any service pack or update level (for example: 9.1, 7.5, 8.0, 18, 19)
    Affected if The exact version cannot be determined or is at or below the affected version thresholds
  3. Compare version against affected ranges for V9.1 products
    If the product is Openpcs 7, Simatic Batch, Simatic Pcs 7, or Simatic Route Control, check if the version is 9.1 or lower. These require V9.1 SP2 UC05 or later to be patched
    Affected if The installed version is 9.1 or any sub-version below 9.1 SP2 UC05
  4. Compare version against affected ranges for Wincc
    If the product is Simatic Wincc, check if the version is exactly 7.4, 7.5, or 8.0. WinCC V7.4 has no patch available per the advisory
    Affected if The installed version matches 7.4, 7.5, or 8.0 (or is below patched levels: V7.5 SP2 Update 15, V8.0 Update 4)
  5. Compare version against affected ranges for Wincc Runtime Professional
    If the product is Simatic Wincc Runtime Professional, check if the version is 18 or 19. These require V18 Update 4 or V19 Update 2 to be patched
    Affected if The installed version is 18 (any sub-version below Update 4) or exactly 19 (below Update 2)

A user is affected if they have any of the listed products installed AND the installed version falls within the vulnerable version ranges without the corresponding patched update applied.

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

Apply vendor patches: upgrade to V9.1 SP2 UC05 or later for V9.1 products, V18 Update 4/V19 Update 2 for WinCC Runtime Professional, V7.5 SP2 Update 15 for WinCC V7.5, V8.0 Update 4 for WinCC V8.0; WinCC V7.4 has no patch available per advisory - contact vendor for mitigations.

Recommended fix High confidence

V9.1 SP2 UC05 (for V9.1 products); V18 Update 4 (for WinCC Runtime Professional V18); V19 Update 2 (for WinCC Runtime Professional V19); V7.5 SP2 Update 15 (for WinCC V7.5); V8.0 Update 4 (for WinCC V8.0)

  1. For OpenPCS 7 V9.1: Upgrade to V9.1 SP2 UC05 or later
  2. For SIMATIC BATCH V9.1: Upgrade to V9.1 SP2 UC05 or later
  3. For SIMATIC PCS 7 V9.1: Upgrade to V9.1 SP2 UC05 or later
  4. For SIMATIC Route Control V9.1: Upgrade to V9.1 SP2 UC05 or later
  5. For SIMATIC WinCC V7.4: No patch available - consider upgrading to a supported version (V7.5 or V8.0)
  6. For SIMATIC WinCC V7.5: Upgrade to V7.5 SP2 Update 15 or later
  7. For SIMATIC WinCC V8.0: Upgrade to V8.0 Update 4 or later
  8. For SIMATIC WinCC Runtime Professional V18: Upgrade to V18 Update 4 or later
Caveat Upgrading major versions may require testing of existing projects; WinCC V7.4 has no patch and requires migration to a supported version

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

Fix this in Openpcs 7 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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