dbcve.org
Jazz Reporting ServiceApplication · Ibm

CVE-2015-7465

HIGH · 8.8 CVSS v3.0 Published 2016-01-10
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
Cross-site request forgery (CSRF) vulnerability in Lifecycle Query Engine (LQE) in IBM Jazz Reporting Service (JRS) 6.0 before 6.0.0-Rational-CLM-ifix005 allows remote authenticated users to hijack the authentication of arbitrary users for requests that insert XSS sequences.

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

CSRF vulnerability in IBM Jazz Reporting Service 6.0 Lifecycle Query Engine allows authenticated attackers to craft malicious requests that hijack other users' sessions and inject XSS sequences. The lack of proper anti-CSRF token validation on state-changing endpoints enables attackers to force authenticated users to perform unauthorized actions.

MitigationApply IBM fix 6.0.0-Rational-CLM-ifix005 or later. If patching is not feasible, implement anti-CSRF tokens on all POST/PUT/DELETE endpoints in LQE and configure the application to validate the Origin/Referer headers.

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
Jazz Reporting ServiceApplication
Affected:= 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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 Jazz Reporting Service installation
    Locate the IBM Jazz Reporting Service installation directory or check running services for processes related to Jazz Reporting Service (commonly found under the /server directory of CLM installations)
    Affected if The product is not installed or is a different version than 6.0
  2. Verify installed version is exactly 6.0
    Check the version information in the Jazz Reporting Service about panel, installation manifest, or version file (typically found in the installation root or through the admin web interface under About > Version)
    Affected if Installed version is exactly 6.0 (matches the affected version range)
  3. Confirm Lifecycle Query Engine (LQE) component is enabled
    Access the Jazz Reporting Service admin console and verify that the Lifecycle Query Engine component is installed and active (typically accessible via the web UI at /lqe or through the CLM administration page)
    Affected if LQE is enabled and running - the CSRF vulnerability applies specifically to LQE state-changing endpoints
  4. Inspect state-changing endpoints for missing anti-CSRF tokens
    Review the HTTP responses from POST, PUT, and DELETE endpoints in LQE (such as data source configuration, query save, or report management endpoints) using browser developer tools or a proxy to check if forms/requests include anti-CSRF tokens
    Affected if State-changing requests do not require valid anti-CSRF tokens - the vulnerability is present
  5. Check for Origin/Referer header validation configuration
    Examine the LQE configuration files (typically in the web.xml or server configuration) to determine whether the application validates the Origin or Referer headers on incoming requests
    Affected if Origin/Referer header validation is not configured or is disabled

If IBM Jazz Reporting Service version 6.0 is running with LQE enabled and state-changing endpoints lack anti-CSRF token validation, the environment is affected by CVE-2015-7465.

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

Apply IBM fix 6.0.0-Rational-CLM-ifix005 or later. If patching is not feasible, implement anti-CSRF tokens on all POST/PUT/DELETE endpoints in LQE and configure the application to validate the Origin/Referer headers.

Fix this in Jazz Reporting Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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