dbcve.org
Business HubApplication · Knime

CVE-2024-6598

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 1.10.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial-of-service vulnerability in KNIME Business Hub 1.10.0-1.10.1 allows authenticated attackers with job execution privileges to execute specially crafted jobs that cause internal message queues to accumulate indefinitely until system resources are exhausted, resulting in outage of most functionality.

MitigationUpgrade to KNIME Business Hub 1.10.2 or later. Since manual administrator intervention is required for recovery if exploited, ensure incident response procedures are documented and consider implementing monitoring for abnormal message queue growth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Business HubApplication
Affected:>= 1.10.0, < 1.10.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify KNIME Business Hub installation and version
    Locate the KNIME Business Hub installation directory and check the version file or use the product's administration interface to determine the installed version number.
    Affected if The installed version is 1.10.0 or 1.10.1 (any version >=1.10.0 but <1.10.2)
  2. Confirm product is running
    Verify that the KNIME Business Hub service is actively running and accessible via its web interface or API.
    Affected if The product is running and accessible to users
  3. Verify authentication is enabled
    Check the KNIME Business Hub security configuration to confirm user authentication is enabled, not left in an open or disabled state.
    Affected if Authentication is enabled and users can log in to the system
  4. Check for job execution privileges in use
    Review user roles and permissions configuration to confirm that any non-admin users have job execution privileges assigned.
    Affected if There are authenticated users with job execution privileges capable of submitting jobs
  5. Inspect for message queue accumulation
    Monitor system resource usage and internal service metrics, specifically looking for abnormally growing message queue backlogs or memory consumption that does not clear after job completion.
    Affected if Message queues are growing abnormally or system resources are being consumed without clearing after jobs complete

A user is affected if they are running KNIME Business Hub version 1.10.0 or 1.10.1 and have authenticated users with job execution privileges, especially if abnormal message queue growth is observed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.10.2 or later
Fixed in 1.10.2
Interim mitigation

Upgrade to KNIME Business Hub 1.10.2 or later. Since manual administrator intervention is required for recovery if exploited, ensure incident response procedures are documented and consider implementing monitoring for abnormal message queue growth.

Recommended fix High confidence

KNIME Business Hub 1.10.2 or later

  1. Back up the current KNIME Business Hub installation and all data
  2. Download KNIME Business Hub version 1.10.2 or later from the official KNIME source
  3. Stop the KNIME Business Hub service
  4. Install the upgrade following the standard KNIME upgrade procedure
  5. Restart the KNIME Business Hub service
  6. Verify the upgrade was successful and the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Business Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6598 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6598 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data