dbcve.org
Knime Analytics PlatformApplication · Knime

CVE-2022-31500

HIGH · 7.8 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to 4.6.0 or later.
See remediation →
80/100
Remediation priority · High
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
In KNIME Analytics Platform below 4.6.0, the Windows installer sets improper filesystem permissions.

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 · moderate confidence

The KNIME Analytics Platform Windows installer below version 4.6.0 sets improper filesystem permissions, likely granting overly permissive access rights to installed files and directories. This vulnerability could allow local users to read, modify, or delete sensitive files they should not have access to, potentially leading to privilege escalation or information disclosure.

MitigationUpgrade KNIME Analytics Platform to version 4.6.0 or later, which contains a corrected installer with proper permission settings. For existing installations, audit and remediate filesystem permissions on the KNIME installation directory.

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
Knime Analytics PlatformApplication
Affected:< 4.6.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Locate KNIME Analytics Platform installation directory
    Check common installation paths on Windows: C:\Program Files\KNIME, C:\Program Files (x86)\KNIME, or the custom path if a custom installation was performed. Use File Explorer or run: dir /s /b "C:\Program Files\KNIME" 2>nul
    Affected if KNIME Analytics Platform is found in the filesystem
  2. Identify installed KNIME version
    Open the installation directory and locate a version file. Check for a version.txt, .install4j, or similar version marker file. Alternatively, right-click the KNIME executable (knime.exe) in the installation folder, select Properties, and view the Details tab for the version number
    Affected if Version number returned is lower than 4.6.0 (e.g., 4.5.0, 4.4.0, etc.)
  3. Confirm Windows installer was used for initial setup
    Determine if KNIME was installed using the Windows installer (.exe or .msi package) rather than a portable or manual extraction. Check Program and Features (appwiz.cpl) for 'KNIME Analytics Platform' entry, or look for typical installer-created files like uninstall information in the installation directory
    Affected if Windows installer was used for the initial installation and version is below 4.6.0
  4. Review filesystem permissions on KNIME installation folder
    Right-click the KNIME installation folder in File Explorer, select Properties, then go to the Security tab. Check which users and groups have access and what permissions they hold. Look for overly broad permissions such as 'Everyone' or 'Users' group with Full Control or Modify access to the directory and its contents
    Affected if Users other than Administrators or the installing user have excessive permissions (Full Control, Modify) on the KNIME installation directory

A user is affected if KNIME Analytics Platform version below 4.6.0 was installed using the Windows installer, and the installation directory grants overly permissive filesystem access to non-admin users.

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 4.6.0 or later
Fixed in 4.6.0
Interim mitigation

Upgrade KNIME Analytics Platform to version 4.6.0 or later, which contains a corrected installer with proper permission settings. For existing installations, audit and remediate filesystem permissions on the KNIME installation directory.

Recommended fix Moderate confidence

4.6.0

  1. 1. Back up your KNIME workspace and any installed custom extensions or plugins
  2. 2. Download KNIME Analytics Platform version 4.6.0 or later from the official knime.com website
  3. 3. Uninstall the current KNIME version using Windows Add/Remove Programs, or simply install the new version to a new directory
  4. 4. Run the new installer with administrator privileges
  5. 5. Follow the installation wizard to complete the upgrade
  6. 6. Restore your backed-up workspace and reinstall any custom extensions as needed
  7. 7. Verify the installation and confirm filesystem permissions are properly restricted

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

Fix this in Knime Analytics Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31500 — 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-2022-31500 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