# CVE-2022-44749: Opening workflows from untrusted resources may override arbitrary file system contents

> Opening a malicious KNIME workflow allows attackers to overwrite arbitrary files via Zip-Slip, potentially leading to data corruption or remote code execution.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Nov 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-4858-5fjj-3758

## What is CVE-2022-44749?

CVE-2022-44749 is a medium-severity path traversal vulnerability in KNIME Analytics Platform, published on 24 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A directory traversal vulnerability in the ZIP archive extraction routines of KNIME Analytics Platform 3.2.0 and above can result in arbitrary files being overwritten on the user's system. This vulnerability is also known as 'Zip-Slip'.

An attacker can create a KNIME workflow that, when being opened by a user, can overwrite arbitrary files that the user has write access to. It's not necessary to execute the workflow, opening the workflow is sufficient. The user will notice that something is wrong because an error is being reported but only after the files have already been written.

This can impact data integrity (file contents are changed) or cause errors in other software (vital files being corrupted). It can even lead to remote code execution if executable files are being replaced and subsequently executed by the user. In all cases the attacker has to know the location of files on the user's system, though.

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

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

It affects 1 product.


Products: Knime Knime Analytics Platform.

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

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

## Is CVE-2022-44749 being exploited?

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

## Other vulnerabilities in KNIME Analytics Platform

- [CVE-2022-31500](https://insights.sbomify.com/CVE-2022-31500/): Misconfiguration in n/a (high 7.8)
- [CVE-2023-5562](https://insights.sbomify.com/CVE-2023-5562/): Unsafe default allows for cross-site scripting attacks in KNIME Server and KNIME Business Hub (medium 6.1)
- [CVE-2021-45096](https://insights.sbomify.com/CVE-2021-45096/): XML external entity in n/a (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44749 is a medium-severity path traversal vulnerability in KNIME Analytics Platform, published on 24 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-44749 in the wild and no public exploit code.

Affected product: KNIME Analytics Platform. 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-44749/ (Markdown: https://insights.sbomify.com/CVE-2022-44749/index.md)
```

## Sources

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

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