dbcve.org
Pi ServerApplication · Aveva

CVE-2023-34348

HIGH · 7.5 CVSS v3.1 Published 2024-01-18
Fix available
A fix is available. Upgrade to 2018 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
AVEVA PI Server versions 2023 and 2018 SP3 P05 and prior contain a vulnerability that could allow an unauthenticated user to remotely crash the PI Message Subsystem of a PI Server, resulting in a denial-of-service condition.

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

AVEVA PI Server versions 2023 and 2018 SP3 P05 and prior contain a vulnerability that allows an unauthenticated remote attacker to crash the PI Message Subsystem, causing a denial-of-service condition. The attack requires no authentication and can be launched remotely.

MitigationUpdate AVEVA PI Server to a version newer than 2018 SP3 P05 and 2023. Additionally, implement network segmentation and firewall controls to limit exposure of the PI Server to untrusted networks.

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
Pi ServerApplication
Affected:< 2018= 2018= 2023

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

CVSS:3.1/AV:N/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. Confirm AVEVA PI Server is installed
    Check the list of installed software on the system for 'AVEVA PI Server' or look for PI Server directories in Program Files (typically C:\Program Files\AVEVA\PI Server or similar).
    Affected if AVEVA PI Server is present on the system.
  2. Identify the installed PI Server version
    Open the Windows Control Panel, go to Programs and Features, and locate AVEVA PI Server to view the installed version, or check the PI Server documentation for the version command-line tool (pisnapshots or similar).
    Affected if The version is 2018 (any subversion including SP3 P05) or 2023 (any subversion), or any version released prior to these.
  3. Verify the PI Message Subsystem component
    Check if the PI Message Subsystem service (PIMessage) is installed and running. This can be done via Windows Services (services.msc) or by checking for the PI Message Subsystem in the PI Server administration tools.
    Affected if The PI Message Subsystem service exists and is running on the server.
  4. Assess network exposure
    Review firewall rules and network configuration to determine if the PI Message Subsystem ports (typically UDP/TCP 4999 or as configured) are exposed to untrusted or external networks.
    Affected if The PI Message Subsystem is reachable from network segments that contain untrusted or external hosts.

The system is affected if AVEVA PI Server version 2018 (any version including SP3 P05 and prior) or 2023 is installed with the PI Message Subsystem enabled and network-accessible to untrusted sources.

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

Update AVEVA PI Server to a version newer than 2018 SP3 P05 and 2023. Additionally, implement network segmentation and firewall controls to limit exposure of the PI Server to untrusted networks.

Recommended fix Moderate confidence

AVEVA PI Server 2023 (newer than affected release) or PI Server 2018 SP3 P06 or later

  1. 1. Identify the current installed version of AVEVA PI Server by checking the PI System Explorer or running the PI Slicer utility
  2. 2. Contact AVEVA customer support or visit the official AVEVA support portal to obtain the specific patch or upgrade for your version
  3. 3. For PI Server 2018: Upgrade to a version newer than SP3 P05 (e.g., SP3 P06 or later if available)
  4. 4. For PI Server 2023: Upgrade to a version newer than 2023 (check AVEVA support for the latest 2023.x release or subsequent release)
  5. 5. Before applying in production, test the upgrade in a non-production environment
  6. 6. Schedule maintenance window as the PI Message Subsystem restart may cause temporary service interruption
  7. 7. Apply the upgrade following AVEVA's official installation documentation
  8. 8. Verify the PI Message Subsystem is running normally after upgrade
Caveat Review AVEVA release notes for any breaking changes between versions; some upgrades may require corresponding PI Client updates

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

Fix this in Pi Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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