KNIME Business Hub: Use of Hard-coded Password
CVE-2025-2402 is a high-severity use of hard-coded password vulnerability in KNIME Business Hub from KNIME, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 1.13.2, 1.12.3, 1.11.3 as the first without the flaw, so updating KNIME Business Hub to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.39% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update KNIME Business Hub to 1.13.2 or 1.12.3 or 1.11.3 or 1.10.3, whichever matches your release line, or a later version.
- Update Business Hub to 1.10.3 or 1.11.3 or 1.12.3 or 1.13.2, whichever matches your release line, or a later version.
- Read the advisory on knime.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| KNIME | KNIME Business Hub | 1.13.0 up to, but not including, 1.13.2; 1.12.0 up to, but not including, 1.12.3; 1.11.0 up to, but not including, 1.11.3; before 1.10.3 | 1.13.2, 1.12.3, 1.11.3, 1.10.3 |
| Knime | Business Hub | before 1.10.3; 1.11.0 up to, but not including, 1.11.3; 1.12.0 up to, but not including, 1.12.3; 1.13.0 up to, but not including, 1.13.2 | 1.10.3, 1.11.3, 1.12.3, 1.13.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.8 | High | CNA (knime.com) |
| CVSS 3.1 | 8.6 | High | NVD |
Official description
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
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Hard-coded Password
The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound authentication to external components.
How developers prevent this class of flaw
- For outbound authentication: store passwords outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible.
- For inbound authentication: Rather than hard-code a default username and password for first time logins, utilize a first login mode that requires the user to enter a unique strong password.
- Perform access control checks and limit which entities can access the feature that requires the hard-coded password. For example, a feature might only be enabled through the system console instead of through a network connection.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in KNIME Business Hub
- 7.2 High severity
- 7.2 High severity
- 8.8 High severity
Recent Use of Hard-coded Password vulnerabilities
- 9.8 Critical severity
- 8.4 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.3 Critical severity
Spotted an error? Tell us.