dbcve.org
Planning Analytics WorkspaceApplication · Ibm

CVE-2022-22392

HIGH · 7.8 CVSS v3.1 Published 2022-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
IBM Planning Analytics Local 2.0 could allow an attacker to upload arbitrary executable files which, when executed by an unsuspecting victim could result in code execution. IBM X-Force ID: 222066.

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

IBM Planning Analytics Local 2.0 contains an arbitrary file upload vulnerability allowing attackers to upload executable files that can be executed by victims, leading to remote code execution.

MitigationImplement strict server-side file type validation, restrict upload directories to be non-executable, disable script execution in upload paths, and apply principle of least privilege to uploaded files.

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
Planning Analytics WorkspaceApplication
Affected:= 2.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Identify IBM Planning Analytics Workspace installation
    Locate the Planning Analytics Workspace installation directory and check for version information in product metadata, About dialog, or version.txt file
    Affected if The installed version is exactly 2.0.0 (version 2.0)
  2. Verify file upload feature is enabled
    Check the IBM Planning Analytics Workspace configuration files (typically in the config directory) for upload-related settings and ensure the upload functionality is not disabled
    Affected if File upload feature is enabled in the configuration
  3. Inspect upload directory configuration
    Review the application configuration to identify the configured upload directory path and check if it is set to a web-accessible location
    Affected if Upload directory is web-accessible and not configured to a non-executable location
  4. Check script execution restrictions
    Examine web server configuration (IHS/Apache) and upload directory settings to determine if script execution is explicitly disabled in upload paths
    Affected if Script execution is NOT disabled in the upload directory (no execution prevention configured)
  5. Verify file type validation settings
    Review application configuration files for server-side file type validation settings to confirm whether strict validation is implemented
    Affected if No strict server-side file type validation is configured, allowing executable file types to be uploaded

Your environment is affected if you have IBM Planning Analytics Workspace version 2.0 with file upload enabled in a web-accessible directory that lacks script execution restrictions and strict file type validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict server-side file type validation, restrict upload directories to be non-executable, disable script execution in upload paths, and apply principle of least privilege to uploaded files.

Recommended fix Moderate confidence

Upgrade to the fixed release of IBM Planning Analytics Workspace as specified in IBM security bulletin for CVE-2022-22392 (contact IBM Support for specific version)

  1. 1. Identify the current installed version of IBM Planning Analytics Workspace by checking the system documentation or installation files
  2. 2. Navigate to the IBM Support Portal at https://www.ibm.com/support/
  3. 3. Search for IBM Planning Analytics security bulletin or patch for CVE-2022-22392
  4. 4. Download and apply the appropriate security update or upgrade to a fixed version as specified in the IBM security bulletin
  5. 5. After applying the patch/upgrade, verify that the file upload functionality now properly validates file types and restricts executable uploads
  6. 6. Test the Planning Analytics Workspace to ensure normal functionality is maintained after the update
Caveat Review IBM release notes for the fixed version for any configuration or compatibility changes before upgrading

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

Fix this in Planning Analytics Workspace Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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