KNIME Business Hub vulnerabilities

Missing security attributes on sensitive cookies in KNIME Business Hub before version 1.19.0 allow an unauthenticated remote attacker to compromise user sessions if other security issues such as a cross-site scripting vulnerability or a man-in-the-middle attack are present. A workaround is not possible.

KNIME Business Hub before version 1.19.0 allows unrestricted network access between execution contexts. An authenticated remote user can access open network ports on executors in different execution contexts if the executor IP address is known and the ports provide access without further authentication. By default no ports are open, but depending on running workflows ports may be opened and provide an attack surface.

A missing authorization check allows anyone having access to a "link without login" for a DataApp to list and potentially access jobs of other users created by the same link in KNIME Business Hub prior to 1.19.0.

Overly informative error messages in the catalog functionality of KNIME Business Hub prior to version 1.18.5 may allow an authenticated remote attacker to see workflow names if their ID is known.

A flaw in the cross-site request forgery (CSRF) prevention of KNIME Business Hub prior to version 1.19.0 allows an authenticated attacker to perform a CSRF attack with passive user interaction. This means the state of a resource could be changed without the user noticing.

An excessive resource allocation issue in the remote workflow editing capabilities of KNIME Business Hub prior to version 1.19.0 allows an authenticated attacker to exhaust resources on the server side. This leads to intermittent unavailability of workflow execution functionality.

A wrong permission check in KNIME Business Hub before version 1.17.0 allowed an authenticated user to save jobs of other users as if they were saved by the job owner. The attacker must have permissions to access the jobs, but they were saved into the catalog service using the wrong owner permissions, potentially allowing saves into spaces where the attacker lacks write permissions.

An open redirect vulnerability existed in KNIME Business Hub prior to version 1.16.0. An unauthenticated remote attacker could craft a link to a legitimate KNIME Business Hub installation which, when opened by the user, redirects the user to a page of the attacker's choice. The problem has been fixed in KNIME Business Hub 1.16.0.

In KNIME Business Hub prior to 1.16.0, potentially sensitive information in jobs was visible to all team members. Starting with 1.16.0, only job metadata is shown to team members; only the job creator can see all information including in- and output data.

Missing HTTP headers (X-Frame-Options, Content-Security-Policy) in KNIME Business Hub before version 1.4.0 has left users vulnerable to clickjacking. This attack tricks users into clicking on actionable items, redirecting them to another server.