# CVE-2022-40977: PILZ: PASvisu and PMI affected by ZipSlip

> An unauthenticated remote attacker can write arbitrary files via a malicious zip file in PILZ PASvisu Server, compromising data integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Nov 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-hjxv-pvv5-vqv2

## What is CVE-2022-40977?

CVE-2022-40977 is a high-severity path traversal vulnerability in PILZ PASvisu, published on 24 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-40977?

It affects 8 products.


Products: Pilz Pasvisu, Pilz Pmi V507 Firmware, Pilz Pmi V512 Firmware, Pilz Pmi V704e Firmware, Pilz Pmi V707e Firmware, Pilz Pmi V807 Firmware, Pilz Pmi V812 Firmware, Pilz Pmi V815 Firmware.

## How do I fix CVE-2022-40977?

No fix has been published for CVE-2022-40977 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-40977 being exploited?

There is no known exploitation of CVE-2022-40977 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40977 and fix it if it is affected.

What it is: CVE-2022-40977 is a high-severity path traversal vulnerability in PILZ PASvisu, published on 24 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40977 in the wild and no public exploit code.

Affected product: PILZ PASvisu. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-40977/ (Markdown: https://insights.sbomify.com/CVE-2022-40977/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-40977
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-40977
- OSV: https://osv.dev/vulnerability/CVE-2022-40977

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-40977/
Summaries are generated and may contain mistakes; the official description above is the record.