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 there were saved by the job owner. The attacker must have permissions to access the jobs but then they were saved into the catalog service using the wrong owner permissions. Therefore it may have been possible to save into spaces where the attacker does not have write permissions. There is no workaround.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:C/RE:M/U:GreenKnime Business Hub
APPKnime< 1.17.0
Related vulnerabilities
A hard-coded, non-random password for the object store (minio) of KNIME Business Hub in all versions except th...
KNIME Business Hub is affected by the Ingress-nginx CVE-2025-1974 ( a.k.a IngressNightmare ) vulnerability whi...
A denial-of-service attack is possible through the execution functionality of KNIME Business Hub 1.10.0 and 1....
An open redirect vulnerability existed in KNIME Business Hub prior to version 1.16.0. An unauthenticated remot...
KNIME Business Hub is affected by several cross-site scripting vulnerabilities in its web pages. If a user cli...