CVE-2024-6598 – Denial-of-service on KNIME Business Hub when certain jobs are executed
https://notcve.org/view.php?id=CVE-2024-6598
A denial-of-service attack is possible through the execution functionality of KNIME Business Hub 1.10.0 and 1.10.1. It allows an authenticated attacker with job execution privileges to execute a job that causes internal messages to pile up until there are no more resources available for processing new messages. This leads to an outage of most functionality of KNIME Business Hub. Recovery from the situation is only possible by manual administrator interaction. Please contact our support for instructions in case you have run into this situation. Updating to KNIME Business Hub 1.10.2 or later solves the problem. • https://www.knime.com/security/advisories#CVE-2024-6598 • CWE-770: Allocation of Resources Without Limits or Throttling •
CVE-2023-5562 – Unsafe default allows for cross-site scripting attacks in KNIME Server and KNIME Business Hub
https://notcve.org/view.php?id=CVE-2023-5562
An unsafe default configuration in KNIME Analytics Platform before 5.2.0 allows for a cross-site scripting attack. When KNIME Analytics Platform is used as an executor for either KNIME Server or KNIME Business Hub several JavaScript-based view nodes do not sanitize the data that is displayed by default. If the data to be displayed contains JavaScript this code is executed in the browser and can perform any operations that the current user is allowed to perform silently. KNIME Analytics Platform already has configuration options with which sanitization of data can be actived, see https://docs.knime.com/latest/webportal_admin_guide/index.html#html-sanitization-webportal https://docs.knime.com/latest/webportal_admin_guide/index.html#html-sanitization-webportal . However, these are off by default which allows for cross-site scripting attacks. KNIME Analytics Platform 5.2.0 will enable sanitization by default. For all previous releases we recommend users to add the corresponding settings to the executor's knime.ini. • https://www.knime.com/security/advisories#CVE-2023-5562 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •
CVE-2023-3140 – KNIME Hub Web Application is vulnerable to clickjacking
https://notcve.org/view.php?id=CVE-2023-3140
Missing HTTP headers (X-Frame-Options, Content-Security-Policy) in KNIME Business Hub before 1.4.0 has left users vulnerable to click jacking. Clickjacking is an attack that occurs when an attacker uses a transparent iframe in a window to trick a user into clicking on an actionable item, such as a button or link, to another server in which they have an identical webpage. The attacker essentially hijacks the user activity intended for the original server and sends them to the other server. • https://www.knime.com/security/advisories#CVE-2023-3140 • CWE-1021: Improper Restriction of Rendered UI Layers or Frames •
CVE-2023-2541 – Sensitive information disclosure in KNIME Hub Web Application
https://notcve.org/view.php?id=CVE-2023-2541
The Web Frontend of KNIME Business Hub before 1.4.0 allows an unauthenticated remote attacker to access internals about the application such as versions, host names, or IP addresses. No personal information or application data was exposed. • https://www.knime.com/security/advisories#CVE-2023-2541 https://zigrin.com/advisories/knime-business-hub-sensitive-information-disclosure • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere •
CVE-2022-44749 – Opening workflows from untrusted resources may override arbitrary file system contents
https://notcve.org/view.php?id=CVE-2022-44749
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. • https://www.knime.com/security/advisories • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •