CVE-2025-2402

A hard-coded, non-random password for the object store (minio) of KNIME Business Hub in all versions except the ones listed below allows an unauthenticated remote attacker in possession of the password to read and manipulate swapped jobs or read and manipulate in- and output data of active jobs. It is also possible to cause a denial-of-service of most functionality of KNIME Business Hub by writing large amounts of data to the object store directly.

There are no viable workarounds therefore we strongly recommend to update to one of the following versions of KNIME Business Hub:

• 1.13.2 or later

• 1.12.3 or later

• 1.11.3 or later

• 1.10.3 or later

Weakness

The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.

Extended Description

There are two main variations of a hard-coded password:

Potential Mitigations

• For inbound authentication: apply strong one-way hashes to your passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When receiving an incoming password during authentication, take the hash of the password and compare it to the hash that you have saved.
• Use randomly assigned salts for each separate hash that you generate. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
• For front-end to back-end connections: Three solutions are possible, although none are complete.

References

• https://www.knime.com/security/advisories#CVE-2025-2402
• https://github.com/advisories/GHSA-v5p7-3387-gpmg