dbcve.org
Pas 4000Operating system · Pilz

CVE-2022-40976

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-24
Fix available
A fix is available. Upgrade to 1.4.0 / 1.4.1 or later.
See remediation →
58/100
Remediation priority · Elevated
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
A path traversal vulnerability was discovered in multiple Pilz products. An unauthenticated local attacker could use a zipped, malicious configuration file to trigger arbitrary file writes ('zip-slip'). File writes do not affect confidentiality or availability.

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

This is a zip-slip vulnerability in Pilz industrial automation products where a path traversal occurs during extraction of zipped configuration files. An unauthenticated local attacker can craft a malicious zip file containing paths with '..' sequences to write files to arbitrary locations outside the intended extraction directory.

MitigationApply vendor-provided patches or firmware updates for affected Pilz products. Implement strict validation of file paths within zip archives before extraction, ensuring extracted paths resolve within the intended target directory.

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
Pas 4000Operating system
Affected:< 1.25.0
PascalApplication
Affected:<= 1.9.1
PasconnectApplication
Affected:< 1.4.0
PasmotionApplication
Affected:< 1.4.1
Pnozmulti ConfiguratorApplication
Affected:< 10.14.4< 11.2.0

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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 Pilz industrial automation products
    Open Windows Control Panel > Programs and Features, or check C:\Program Files and C:\Program Files (x86) for Pilz directories. Look for: PAS 4000, Pascal, PASconnect, PASmotion, or Pnozmulti Configurator.
    Affected if Any of these Pilz products are present on the system
  2. Determine installed version of PAS 4000
    If installed, right-click the application shortcut, select Properties, then look in the Details tab for Version info. Alternatively, check the program's Help > About dialog.
    Affected if Version is lower than 1.25.0
  3. Determine installed version of Pascal
    Check application Properties > Details tab, or look in the installation directory for a version.txt or about file.
    Affected if Version is 1.9.1 or lower
  4. Determine installed version of PASconnect
    Check application Properties > Details tab or Help > About dialog.
    Affected if Version is lower than 1.4.0
  5. Determine installed version of PASmotion
    Check application Properties > Details tab or Help > About dialog.
    Affected if Version is lower than 1.4.1
  6. Determine installed version of Pnozmulti Configurator
    Check application Properties > Details tab or Help > About dialog. Note that there are two version branches: 10.x and 11.x.
    Affected if Version is lower than 10.14.4 (for 10.x branch) or lower than 11.2.0 (for 11.x branch)

The system is affected if any Pilz product from the list is installed with a version falling within the specified vulnerable ranges.

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 1.4.0 / 1.4.1 / 1.25.0 or later
Fixed in 1.4.01.4.11.25.0
Interim mitigation

Apply vendor-provided patches or firmware updates for affected Pilz products. Implement strict validation of file paths within zip archives before extraction, ensuring extracted paths resolve within the intended target directory.

Recommended fix Moderate confidence

Pas 4000: 1.25.0+ | Pascal: 1.9.2+ | Pasconnect: 1.4.0+ | Pasmotion: 1.4.1+ | Pnozmulti Configurator: 10.14.4+ or 11.2.0+

  1. 1. Identify the specific Pilz product(s) in use from the affected list: Pas 4000, Pascal, Pasconnect, Pasmotion, or Pnozmulti Configurator
  2. 2. Determine the current installed version of the affected product(s)
  3. 3. For Pas 4000: upgrade to version 1.25.0 or higher
  4. 4. For Pascal: upgrade to version 1.9.2 or higher
  5. 5. For Pasconnect: upgrade to version 1.4.0 or higher
  6. 6. For Pasmotion: upgrade to version 1.4.1 or higher
  7. 7. For Pnozmulti Configurator: upgrade to version 10.14.4 or higher, or version 11.2.0 or higher
  8. 8. Verify the upgrade was successful by checking the new version number
Caveat Review release notes for any functional changes between current and new versions before upgrading production systems

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

Fix this in Pas 4000 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 the upgrade done

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-2022-40976 — 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-2022-40976 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