CVE-2022-2788
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 · uneditedEmerson Electric's Proficy Machine Edition Version 9.80 and prior is vulnerable to CWE-29 Path Traversal: '\..\Filename', also known as a ZipSlip attack, through an upload procedure which enables attackers to implant a malicious .BLZ file on the PLC. The file can transfer through the engineering station onto Windows in a way that executes the malicious code.
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 confidenceProficy Machine Edition versions 9.80 and prior contain a path traversal vulnerability (CWE-29, ZipSlip) in its file upload procedure. Attackers can craft malicious .BLZ files containing paths with '..\' sequences that escape the intended upload directory during extraction. These files can be planted on PLCs and transferred to the engineering station, allowing arbitrary code execution on Windows systems.
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<= 9.80CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Proficy Machine Edition is installedCheck the system for Proficy Machine Edition installation by looking in standard program directories (e.g., C:\Program Files\GE Digital\Proficy Machine Edition) or check Add/Remove Programs for 'Proficy Machine Edition' or 'GE Digital Proficy' entriesAffected if Proficy Machine Edition is found on the system
-
Determine the installed versionLocate the installed Proficy Machine Edition version by checking the program's About dialog, version info in the executable, or installation metadata in the Windows registry under the Proficy installation keyAffected if The installed version is 9.80 or any version prior to 9.80
-
Verify .BLZ file import functionality is presentCheck if the Proficy Machine Edition installation includes the capability to import or open .BLZ backup/archive files, which is the attack vector for this vulnerabilityAffected if The .BLZ file import feature exists in the installed version and users have access to import .BLZ files from external sources or PLCs
-
Inspect for suspicious .BLZ filesReview any .BLZ files present on the system or recently transferred from PLCs for abnormal file sizes or unexpected contents; use archive inspection tools to examine .BLZ files for path entries containing '..\' sequences before extractionAffected if Any .BLZ files contain path traversal sequences ('..\') that could escape the intended extraction directory
-
Check for signs of code executionReview the Proficy installation directory and Windows temporary folders for newly created or modified executable files that were not intentionally placed there, especially after .BLZ file imports have occurredAffected if Unexpected executables or scripts exist in directories outside the intended Proficy working folders
You are affected if Proficy Machine Edition version 9.80 or prior is installed and the system processes .BLZ files from untrusted sources, as the path traversal vulnerability allows arbitrary file writes during extraction.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict path validation and sanitization during file upload/extraction to prevent directory traversal; validate that extracted files remain within the intended base directory and reject any paths containing '..' sequences. Consider using safe archive extraction libraries that prevent ZipSlip attacks.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2788 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2788 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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