dbcve.org
Jazz Reporting ServiceApplication · Ibm

CVE-2016-0350

MEDIUM · 5.4 CVSS v3.0 Published 2016-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 scripting (XSS) vulnerability in the Report Builder and Data Collection Component (DCC) in IBM Jazz Reporting Service (JRS) 5.x before 5.0.2 ifix016 and 6.x before 6.0.1 ifix005 allows remote authenticated users to inject arbitrary web script or HTML via a crafted URL, a different vulnerability than CVE-2016-2888 and CVE-2016-0313.

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

Cross-site scripting (XSS) vulnerability in IBM Jazz Reporting Service's Report Builder and Data Collection Component allows authenticated users to inject arbitrary web script or HTML via crafted URLs. The vulnerability affects versions 5.x before 5.0.2 ifix016 and 6.x before 6.0.1 ifix005.

MitigationApply the vendor-supplied ifixes (5.0.2 ifix016 for v5.x or 6.0.1 ifix005 for v6.x) or upgrade to later fixed versions to remediate the XSS vulnerability.

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:= 5.0= 5.0.1= 5.0.2= 6.0= 6.0.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Confirm IBM Jazz Reporting Service is installed
    Check your IBM Jazz-based server for the presence of Jazz Reporting Service by reviewing installed applications in the IBM Jazz Team Server administrative console or checking for the 'rs' folder in the IBM Jazz installation directory.
    Affected if Jazz Reporting Service is not installed on the system.
  2. Identify the installed Jazz Reporting Service version
    Access the IBM Jazz Team Server administrative console, navigate to the Jazz Reporting Service application, and view the version information from the installed applications list. Alternatively, check the about.html or version file within the Jazz Reporting Service installation directory.
    Affected if The installed version matches 5.0, 5.0.1, 5.0.2, 6.0, or 6.0.1.
  3. Determine if Report Builder is enabled
    Log into the Jazz Reporting Service web interface and check if the Report Builder module is accessible or enabled for authenticated users. This is typically found under the reporting or authoring sections of the web application.
    Affected if Report Builder is accessible to authenticated users in the affected version.
  4. Determine if Data Collection Component is enabled
    Check the Jazz Reporting Service configuration to see if the Data Collection Component is running or configured. This can be verified through the Jazz Team Server admin console under the Data Collection Component service status.
    Affected if Data Collection Component is running in the affected version.
  5. Check if vendor ifixes have been applied
    Review the installed ifixes for Jazz Reporting Service. In the Jazz Team Server admin console, navigate to the ifix status or check the ifix directory within the Jazz Reporting Service installation folder for ifix016 (for v5.x) or ifix005 (for v6.x).
    Affected if Neither ifix016 (for v5.x) nor ifix005 (for v6.x) is listed as installed.

The environment is affected if IBM Jazz Reporting Service is installed with version 5.0, 5.0.1, 5.0.2, 6.0, or 6.0.1, Report Builder or Data Collection Component is enabled, and the corresponding vendor ifix has not been applied.

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 the vendor-supplied ifixes (5.0.2 ifix016 for v5.x or 6.0.1 ifix005 for v6.x) or upgrade to later fixed versions to remediate the XSS vulnerability.

Fix this in Jazz Reporting Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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