dbcve.org
Planning Analytics WorkspaceApplication · Ibm

CVE-2024-35143

CRITICAL · 9.1 CVSS v3.1 Published 2024-08-04
Fix available
A fix is available. Upgrade to 2.0.97 / 2.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
IBM Planning Analytics Local 2.0 and 2.1 connects to a MongoDB server. MongoDB, a document-oriented database system, is listening on the remote port, and it is configured to allow connections without password authentication. A remote attacker can gain unauthorized access to the database. IBM X-Force ID: 292420.

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 and 2.1 connects to a MongoDB database server that is configured to allow connections without password authentication. A remote attacker can directly connect to the exposed MongoDB instance and gain full unauthorized access to all data within the database.

MitigationEnable MongoDB authentication with strong credentials and restrict network access to only trusted clients. Update connection strings in the IBM Planning Analytics configuration to use authenticated connections.

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, < 2.0.97>= 2.1, < 2.1.4
Planning Analytics LocalApplication
Affected:>= 2.0, < 2.0.97>= 2.1.0, < 2.1.4

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

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

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 version
    Check the installed version of IBM Planning Analytics Workspace or Local. On Windows, this can often be found in the installation directory or via the IBM Planning Analytics menu under 'About'. Alternatively, check the version file in the installation path (commonly in the pAInstall or similar directory).
    Affected if The installed version is >= 2.0 and < 2.0.97, or >= 2.1.0 and < 2.1.4
  2. Locate the MongoDB connection configuration
    Find the configuration file used by IBM Planning Analytics to connect to MongoDB. Common locations include the Tomcat configuration directory (context.xml or server.xml), or the Planning Analytics data directory. Look for MongoDB connection strings in configuration files.
    Affected if Configuration files contain MongoDB connection parameters (host, port, database name)
  3. Verify MongoDB authentication status
    Check the MongoDB configuration file (mongod.conf) or connect to the MongoDB instance directly using the mongo shell and run 'db.getUsers()' to see if any users are defined. Also check if the connection string in Planning Analytics includes credentials.
    Affected if No users are defined in MongoDB (db.getUsers() returns empty) OR the MongoDB connection string from Planning Analytics does not include username/password credentials

The environment is affected if IBM Planning Analytics version is within 2.0 to < 2.0.97 or 2.1.0 to < 2.1.4 AND the connected MongoDB instance has authentication disabled or the connection does not use credentials.

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 2.0.97 / 2.1.4 or later
Fixed in 2.0.972.1.4
Interim mitigation

Enable MongoDB authentication with strong credentials and restrict network access to only trusted clients. Update connection strings in the IBM Planning Analytics configuration to use authenticated connections.

Recommended fix Moderate confidence

Planning Analytics Workspace 2.0.97+ or 2.1.4+ / Planning Analytics Local 2.0.97+ or 2.1.4+

  1. Identify currently installed Planning Analytics Workspace and/or Planning Analytics Local version using system information or admin console
  2. For Planning Analytics Workspace 2.0.x users: Upgrade to version 2.0.97 or later
  3. For Planning Analytics Workspace 2.1.x users: Upgrade to version 2.1.4 or later
  4. For Planning Analytics Local 2.0.x users: Upgrade to version 2.0.97 or later
  5. For Planning Analytics Local 2.1.x users: Upgrade to version 2.1.4 or later
  6. After upgrade, verify MongoDB connection now requires authentication by attempting an unauthenticated connection (should fail)
  7. Consult IBM documentation for any specific upgrade prerequisites or migration steps for your version
Caveat Review IBM release notes for the target version for any breaking changes or migration requirements 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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