dbcve.org
Knime Analytics PlatformApplication · Knime

CVE-2022-44749

HIGH · 7.0 CVSS v3.1 Published 2022-11-24
Fix available
A fix is available. Upgrade to 4.6.4 or later.
See remediation →
73/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 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.

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

A Zip-Slip directory traversal vulnerability exists in KNIME Analytics Platform's ZIP archive extraction routines (version 3.2.0+). When a user opens a malicious KNIME workflow (a ZIP file), the extraction process fails to validate paths, allowing the attacker to write files outside the intended directory via '..' sequences in filenames, overwriting arbitrary files the user has access to.

MitigationUpgrade to the patched version of KNIME Analytics Platform that properly validates and sanitizes ZIP entry paths before extraction, rejecting entries with directory traversal sequences.

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
Knime Analytics PlatformApplication
Affected:>= 3.2.0, < 4.6.4

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify KNIME Analytics Platform version
    Open KNIME and go to Help > About KNIME Analytics Platform, or check the installation directory for a version file. Alternatively, run 'knime.exe -version' or check the product name in Add/Remove Programs (Windows) orApplications folder (Mac).
    Affected if The installed version is 3.2.0 or higher but lower than 4.6.4
  2. Confirm workflow file usage
    Check if the user works with .knwf files (KNIME workflow archives), which are ZIP files containing workflow components.
    Affected if The user opens or imports .knwf workflow files from any source
  3. Assess source of workflow files
    Review whether workflows are obtained from the KNIME Hub, community forums, email attachments, or other external/untrusted sources.
    Affected if Workflows are sourced from anywhere other than the official KNIME Hub with verified publishers, or from untrusted recipients
  4. Verify ZIP extraction behavior
    Attempt to extract a test ZIP file containing '..' sequences in filenames using KNIME's workflow import function. Monitor whether files are written outside the intended workflow directory.
    Affected if Files are created outside the workflow extraction directory when '..' sequences are present in archive entries

The environment is affected if KNIME Analytics Platform version is 3.2.0 or higher but lower than 4.6.4, and users open or import KNIME workflow (.knwf) files from any source, particularly untrusted ones.

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 4.6.4 or later
Fixed in 4.6.4
Interim mitigation

Upgrade to the patched version of KNIME Analytics Platform that properly validates and sanitizes ZIP entry paths before extraction, rejecting entries with directory traversal sequences.

Recommended fix High confidence

4.6.4 or later

  1. Download KNIME Analytics Platform version 4.6.4 or later from the official KNIME website (www.knime.com)
  2. Install the new version, replacing the affected installation
  3. After upgrading, verify that workflows can be opened without errors
  4. Consider backing up existing workflows before opening untrusted workflow files in the future

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

Fix this in Knime Analytics Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44749 — 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-44749 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