dbcve.org
Planning AnalyticsApplication · Ibm

CVE-2019-4613

HIGH · 8.8 CVSS v3.1 Published 2020-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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 2.0 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 168524.

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 2.0 contains a cross-site request forgery (CSRF) vulnerability that allows attackers to trick authenticated users into executing unintended actions. The lack of proper anti-CSRF tokens or origin validation enables malicious requests to be processed as legitimate user actions.

MitigationImplement anti-CSRF tokens for all state-changing operations, enable SameSite cookie attributes, and validate Origin/Referer headers to prevent forged requests from untrusted domains.

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

CVSS:3.1/AV:N/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 installation and version
    Locate the IBM Planning Analytics installation directory and check the version information file, or run the product version command if available. Common paths may include C:\Program Files\IBM\Planning Analytics or /opt/ibm/planninganalytics.
    Affected if The installed version is exactly 2.0 (matches = 2.0 range).
  2. Confirm TM1 Web interface is accessible
    Check if the TM1 Web or WA (Web Architecture) component is running and reachable. Attempt to access the web interface URL (typically port 9510 or 8000 by default) from a browser or curl request.
    Affected if The web interface is exposed and accepts authentication, as CSRF attacks target authenticated sessions.
  3. Inspect HTTP response headers for SameSite cookie attributes
    Log into the IBM Planning Analytics web interface using a browser, open developer tools (F12), go to the Network tab, and examine the Set-Cookie headers in responses. Look for SameSite=Strict or SameSite=Lax attributes.
    Affected if Cookies are missing SameSite attributes or set to SameSite=None without the Secure flag, indicating missing CSRF protection.
  4. Verify Origin or Referer header validation exists
    Send a state-changing request (such as a cube action or process execution) with a manipulated Origin header (e.g., Origin: http://malicious-site.com) using a tool like Burp Suite or curl to see if the request is rejected.
    Affected if Requests with arbitrary Origin headers are processed without validation, confirming the lack of origin checking.
  5. Check for anti-CSRF token presence in forms or APIs
    Log into the web interface, capture a state-changing request, and inspect whether a CSRF token, security token, or unique request identifier is included in the request parameters or headers.
    Affected if No anti-CSRF tokens are present in POST requests or API calls that modify data.

A user is affected if IBM Planning Analytics version 2.0 is installed with the web interface enabled and lacks SameSite cookie attributes, Origin/Referer validation, and anti-CSRF tokens in state-changing requests.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens for all state-changing operations, enable SameSite cookie attributes, and validate Origin/Referer headers to prevent forged requests from untrusted domains.

Fix this in Planning Analytics Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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