dbcve.org
Pi Asset Framework ClientApplication · Aveva

CVE-2024-3467

HIGH · 7.8 CVSS v3.1 Published 2024-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
There is a vulnerability in AVEVA PI Asset Framework Client that could allow malicious code to execute on the PI System Explorer environment under the privileges of an interactive user that was socially engineered to import XML supplied by an attacker.

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 · moderate confidence

The vulnerability allows execution of malicious code through specially crafted XML files imported into AVEVA PI Asset Framework Client via PI System Explorer. An attacker leverages social engineering to trick an authenticated user into importing attacker-supplied XML, which then executes under that user's privileges. This is likely an XML external entity (XXE) or code injection flaw in the XML parser that fails to sanitize malicious content.

MitigationOrganizations should train users to never import XML from untrusted sources, implement strict input validation for XML imports, and apply vendor patches when available. Consider disabling or restricting XML import functionality if not operationally required.

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 Asset Framework ClientApplication
Affected:= 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 AVEVA PI Asset Framework Client version
    Open Windows Control Panel > Programs and Features, or use the 'Get-ItemProperty' PowerShell cmdlet: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*AVEVA*PI*Asset*Framework*'}
    Affected if The installed version is 2018 or 2023 (any patch level within these major versions)
  2. Confirm PI System Explorer is deployed
    Check for the presence of PI System Explorer (pse.exe) on the workstation. Common paths include: C:\Program Files\AVEVA\PI System\PI System Explorer\pse.exe or within the AVEVA installation directory. Use: Get-ChildItem -Path 'C:\Program Files\AVEVA' -Filter 'pse.exe' -Recurse -ErrorAction SilentlyContinue
    Affected if PI System Explorer executable exists on the system, indicating the client component is installed
  3. Verify user access to XML import functionality
    Launch PI System Explorer and attempt to locate the XML import feature. Typically found under File > Import > Import from XML, or via right-click context menus in the navigation pane. Document whether the import option is visible and accessible to standard users
    Affected if The XML import option is available and accessible to authenticated users in PI System Explorer
  4. Check for recent XML import activity
    Review Windows Event Logs under Application and Security logs for Event IDs related to PI System Explorer or AVEVA PI imports. Also check file system for recently modified XML files in user-accessible directories: %USERPROFILE%\Documents\PI\, or shared PI Data Archive folders
    Affected if XML files have been imported recently, indicating the attack vector could have been exploited

The environment is affected if AVEVA PI Asset Framework Client version 2018 or 2023 is installed and PI System Explorer with XML import capability is accessible to authenticated users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should train users to never import XML from untrusted sources, implement strict input validation for XML imports, and apply vendor patches when available. Consider disabling or restricting XML import functionality if not operationally required.

Fix this in Pi Asset Framework Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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