CVE-2022-40977
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 · uneditedA path traversal vulnerability was discovered in Pilz PASvisu Server before 1.12.0. An unauthenticated remote 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 · high confidenceA zip-slip path traversal vulnerability exists in Pilz PASvisu Server versions before 1.12.0, allowing unauthenticated remote attackers to achieve arbitrary file writes by uploading a specially crafted malicious configuration zip file during the import process.
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< 1.12.0<= 1.3.58<= 1.3.58< 2.2.0< 2.2.0< 1.6.102< 1.6.102< 1.6.102CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed productDetermine if the system is running Pilz PASvisu Server or a Pilz Pmi device (V507, V512, V704e, V707e, V807, V812, V815)Affected if The product is any of the listed Pilz products and the version falls below the fixed versions
-
Check PASvisu Server versionLocate the PASvisu Server installation directory and check the version information, typically found in the software about page, an installer file, or a version file within the program directoryAffected if PASvisu Server version is below 1.12.0
-
Check Pmi firmware versionAccess the Pmi device web interface or use the manufacturer's diagnostic tool to retrieve the firmware version informationAffected if Firmware version is: Pmi V507 <= 1.3.58, Pmi V512 <= 1.3.58, Pmi V704e < 2.2.0, Pmi V707e < 2.2.0, Pmi V807 < 1.6.102, Pmi V812 < 1.6.102, or Pmi V815 < 1.6.102
-
Verify if configuration import feature is accessibleCheck whether the PASvisu web interface allows unauthenticated or authenticated users to access the configuration import/upload functionalityAffected if The import feature is exposed and accessible to users
-
Inspect for suspicious uploaded filesReview the PASvisu upload directory and system for any unexpected configuration files, scripts, or modified files that may indicate exploitation of the zip-slip vulnerabilityAffected if Unexpected files exist outside the expected upload directory, or configuration files contain paths outside the intended directory
The environment is affected if running any Pilz PASvisu Server version below 1.12.0 or any of the listed Pmi firmware versions, and the configuration import feature is accessible.
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 data1.6.1021.12.02.2.0
Upgrade Pilz PASvisu Server to version 1.12.0 or later to obtain the patch for this vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40977 — 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-40977 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