dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2017-5532

MEDIUM · 5.4 CVSS v3.0 Published 2017-11-15
Fix available
A fix is available. Upgrade to after 6.4.1 or later.
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
A vulnerability in the report renderer component of TIBCO JasperReports Server, TIBCO JasperReports Server Community Edition, TIBCO JasperReports Server for ActiveMatrix BPM, TIBCO JasperReports Library, TIBCO JasperReports Library for ActiveMatrix BPM, TIBCO Jaspersoft for AWS with Multi-Tenancy, TIBCO Jaspersoft Reporting and Analytics for AWS, TIBCO Jaspersoft Studio, and TIBCO Jaspersoft Studio for ActiveMatrix BPM may allow a subset of authorized users to perform persistent cross-site scripting (XSS) attacks. Affected releases are TIBCO JasperReports Server 6.2.3 and below; 6.3.0; 6.3.1; 6.3.2; 6.4.0, TIBCO JasperReports Server Community Edition 6.4.0 and below, TIBCO JasperReports Server for ActiveMatrix BPM 6.4.0 and below, TIBCO JasperReports Library 6.2.3 and below; 6.3.0; 6.3.1; 6.3.2; 6.4.0; 6.4.1, TIBCO JasperReports Library for ActiveMatrix BPM 6.4.1 and below, TIBCO Jaspersoft for AWS with Multi-Tenancy 6.4.0 and below, TIBCO Jaspersoft Reporting and Analytics for AWS 6.4.0 and below, TIBCO Jaspersoft Studio 6.2.3 and below; 6.3.0; 6.3.1; 6.3.2; 6.4.0, and TIBCO Jaspersoft Studio for ActiveMatrix BPM 6.4.0 and below.

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

A persistent cross-site scripting (XSS) vulnerability exists in the report renderer component of TIBCO JasperReports products. The renderer fails to properly sanitize input, allowing authenticated users to inject malicious scripts that are stored and executed when other users view the affected reports.

MitigationApply vendor patches for the specific JasperReports product version in use. Implement output encoding in report templates and consider Content Security Policy headers as a compensating control until patching is complete.

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
Jasperreports ServerApplication
Affected:<= 6.2.3= 6.3.0= 6.3.1= 6.3.2= 6.4.0<= 6.4.0
Jasperreports LibraryApplication
Affected:<= 6.2.3= 6.3.0= 6.3.1= 6.3.2= 6.4.0= 6.4.1<= 6.4.1
JaspersoftApplication
Affected:<= 6.4.0
Jaspersoft Reporting And AnalyticsApplication
Affected:<= 6.4.0
Jaspersoft StudioApplication
Affected:<= 6.2.3= 6.3.0= 6.3.1= 6.3.2= 6.4.0<= 6.4.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
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. Identify the installed JasperReports product and version
    Locate the product's about or version information. For JasperReports Server, check the build number in the admin UI or the manifest file in the installation directory. For JasperReports Library, check the JAR file version or project dependencies. For Jaspersoft Studio, check the application installation details.
    Affected if The installed version matches the affected ranges: JasperReports Server <= 6.2.3, 6.3.0-6.3.2, or 6.4.0; JasperReports Library <= 6.2.3, 6.3.0-6.3.2, 6.4.0-6.4.1; Jaspersoft <= 6.4.0; Jaspersoft Studio <= 6.2.3, 6.3.0-6.3.2, or 6.4.0.
  2. Determine if the report renderer component is in use
    Check if the JasperReports report rendering functionality is active. On JasperReports Server, verify if the report viewing and rendering UI is accessible. In Library deployments, confirm if report generation code is being executed.
    Affected if The report renderer component is enabled and accessible to users.
  3. Verify user authentication is enabled
    Confirm that the JasperReports deployment has authentication configured. For Server installations, check if the login page is active and user accounts exist. For Library-based deployments, verify if any authentication middleware is in place.
    Affected if User authentication is configured and users can log in to access report functionality.
  4. Inspect report output for unsanitized content
    Create or review a test report that includes user-supplied input in report fields. View the rendered output in HTML format and inspect the page source to see if input is properly escaped or rendered as raw HTML/JavaScript.
    Affected if User-supplied input in report fields is rendered without proper HTML encoding, allowing script execution.

A user is affected if they are running any of the listed JasperReports product versions with the report renderer component enabled and authentication configured, particularly if custom reports accept user input that is not validated.

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
Upgrade available Upgrade to a release after 6.4.1
Interim mitigation

Apply vendor patches for the specific JasperReports product version in use. Implement output encoding in report templates and consider Content Security Policy headers as a compensating control until patching is complete.

Fix this in Jasperreports Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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