dbcve.org
Jasperreports Library Community EditionApplication · Tibco

CVE-2017-5529

MEDIUM · 6.5 CVSS v3.0 Published 2017-06-29
Fix available
A fix is available. Upgrade to after 6.4.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
JasperReports library components contain an information disclosure vulnerability. This vulnerability includes the theoretical disclosure of any accessible information from the host file system. Affects TIBCO JasperReports Library Community Edition (versions 6.4.0 and below), TIBCO JasperReports Library for ActiveMatrix BPM (versions 6.2.0 and below), TIBCO JasperReports Professional (versions 6.2.1 and below, and 6.3.0), TIBCO JasperReports Server (versions 6.1.1 and below, 6.2.0, 6.2.1, 6.3.0), TIBCO JasperReports Server Community Edition (versions 6.3.0 and below), TIBCO JasperReports Server for ActiveMatrix BPM (versions 6.2.0 and below), TIBCO Jaspersoft for AWS with Multi-Tenancy (versions 6.3.0 and below), TIBCO Jaspersoft Reporting and Analytics for AWS (versions 6.3.0 and below), and TIBCO Jaspersoft Studio for ActiveMatrix BPM (versions 6.2.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 · moderate confidence

Information disclosure vulnerability in JasperReports library components that could allow reading accessible files from the host file system, likely through path traversal or similar mechanism. Affects multiple TIBCO JasperReports products across various versions.

MitigationUpdate to patched versions of JasperReports library components and implement file system access controls where feasible.

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 Library Community EditionApplication
Affected:<= 6.4.0
Jasperreports Library For Activematrix BpmApplication
Affected:<= 6.2.0
Jasperreports ProfessionalApplication
Affected:<= 6.2.1= 6.3.0
Jasperreports ServerApplication
Affected:<= 6.1.1= 6.2.0= 6.2.1= 6.3.0
Jasperreports Server Community EditionApplication
Affected:<= 6.3.0
Jasperreports Server For Activematrix BpmApplication
Affected:<= 6.2.0
Jaspersoft For Aws With Multi TenancyApplication
Affected:<= 6.3.0
Jaspersoft Reporting And Analytics For AwsApplication
Affected:<= 6.3.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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 JasperReports product and version
    Locate the JasperReports installation directory and check version manifest or about/info files. Common paths include: for Server: <install>/buildomatic/conf.xml or <install>/WEB-INF/web.xml; for Library: check jar file names containing version number or MANIFEST.MF inside jasperreports-*.jar
    Affected if Installed version matches any of the affected ranges: Library CE <= 6.4.0, Library for Activematrix BPM <= 6.2.0, Professional <= 6.2.1 or = 6.3.0, Server <= 6.1.1 or = 6.2.0/6.2.1/6.3.0, Server CE <= 6.3.0, Server for Activematrix BPM <= 6.2.0, AWS variants <= 6.3.0
  2. Verify web reporting interface is exposed
    Check if JasperReports Server web application is deployed and accessible. Look for: Tomcat/webapps/jasperserver or similar servlet container deployment, check HTTP/HTTPS ports (usually 8080, 8443) are listening, inspect server.xml for deployed applications
    Affected if JasperReports web interface (JasperServer) is accessible without additional authentication or has known authentication bypass conditions
  3. Confirm report execution functionality is enabled
    Check if the reporting engine is actively processing report requests. Look for: jasperreports.properties configuration files, scheduler/ Quartz job configurations, any enabled report input or output features
    Affected if Report execution, export, or scheduling features are enabled and processing requests from users or automated processes

You are affected if your installed JasperReports product version falls within the affected ranges AND the web-based reporting interface with file handling capabilities is accessible and enabled.

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.0
Interim mitigation

Update to patched versions of JasperReports library components and implement file system access controls where feasible.

Fix this in Jasperreports Library Community Edition Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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