CVE-2022-44748
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 directory traversal vulnerability in the ZIP archive extraction routines of KNIME Server since 4.3.0 can result in arbitrary files being overwritten on the server's file system. This vulnerability is also known as 'Zip-Slip'. An attacker can create a KNIME workflow that, when being uploaded, can overwrite arbitrary files that the operating system user running the KNIME Server process has write access to. The user must be authenticated and have permissions to upload files to KNIME Server. 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 KNIME Server process user. In all cases the attacker has to know the location of files on the server's file system, though. Note that users that have permissions to upload workflows usually also have permissions to run them on the KNIME Server and can therefore already execute arbitrary code in the context of the KNIME Executor's operating system user. There is no workaround to prevent this vulnerability from being exploited. Updates to fixed versions 4.13.6, 4.14.3, or 4.15.3 are advised.
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 confidenceDirectory traversal (Zip-Slip) vulnerability in KNIME Server's ZIP archive extraction routines allows authenticated users with workflow upload permissions to write files to arbitrary server paths by including path traversal sequences in archive entry names, potentially overwriting system files or achieving code execution.
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>= 4.3.0, < 4.13.6>= 4.14.0, < 4.14.3>= 4.15.0, < 4.15.3CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify KNIME Server installationLocate KNIME Server by checking common installation directories (e.g., /opt/knime-server, C:\Program Files\KNIME, or /usr/local/knime-server) or by identifying the knime-server process running on the system.Affected if KNIME Server is installed on the system
-
Determine installed KNIME Server versionCheck the version file in the KNIME Server installation directory, typically found in a version.txt or manifest file, or access the KNIME Server web interface and navigate to the Server Administration section to view the version information.Affected if The installed version falls within the vulnerable ranges: 4.3.0 to 4.13.5, 4.14.0 to 4.14.2, or 4.15.0 to 4.15.2
-
Verify workflow upload capability is enabledCheck the KNIME Server configuration file (knime-server.config) for the parameter enabling workflow upload or workflow import functionality, typically named knime.server.upload.allowed or similar workflow write permissions.Affected if Workflow upload or import permissions are enabled in the server configuration
-
Confirm existence of users with upload permissionsReview user roles and permissions in the KNIME Server user management section (via the web interface under User Administration) or by inspecting the users.xml and roles.xml configuration files in the server config directory.Affected if Any user accounts are granted workflow upload or workflow import permissions
The environment is affected if KNIME Server is installed with a vulnerable version (4.3.0-4.13.5, 4.14.0-4.14.2, or 4.15.0-4.15.2) and the workflow upload feature is enabled for at least one user.
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.
dbcve · scoped4.13.64.14.34.15.3
Update KNIME Server to fixed versions 4.13.6, 4.14.3, or 4.15.3 which contain the patched ZIP extraction routine; no workaround exists.
Upgrade to version 4.13.6, 4.14.3, or 4.15.3 depending on your current major version branch
- Identify the currently installed KNIME Server version by checking the server administration interface or running 'knime-server --version'
- Determine the appropriate upgrade path based on current version: if 4.3.0-4.13.5 upgrade to 4.13.6; if 4.14.0-4.14.2 upgrade to 4.14.3; if 4.15.0-4.15.2 upgrade to 4.15.3
- Download the corresponding fixed version from the official KNIME download portal (www.knime.com)
- Perform a full backup of the KNIME Server data directory, configuration files, and database (if applicable)
- Stop the KNIME Server service using the appropriate system command (e.g., 'systemctl stop knime-server' or 'service knime-server stop')
- Install the upgraded KNIME Server version following the official installation documentation
- Start the KNIME Server service and verify it is running correctly
- Confirm the vulnerability is patched by checking the server version and reviewing KNIME release notes for the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44748 — 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-44748 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