dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2018-18816

MEDIUM · 5.4 CVSS v3.0 Published 2019-03-07
Fix available
A fix is available. Upgrade to after 7.1.0 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
The repository component of TIBCO Software Inc.'s TIBCO JasperReports Server, TIBCO JasperReports Server Community Edition, TIBCO JasperReports Server for ActiveMatrix BPM, TIBCO Jaspersoft for AWS with Multi-Tenancy, TIBCO Jaspersoft Reporting and Analytics for AWS contains a persistent cross site scripting vulnerability. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Server: versions up to and including 6.3.4; 6.4.0; 6.4.1; 6.4.2; 6.4.3; 7.1.0, TIBCO JasperReports Server Community Edition: versions up to and including 7.1.0, TIBCO JasperReports Server for ActiveMatrix BPM: versions up to and including 6.4.3, TIBCO Jaspersoft for AWS with Multi- Tenancy versions up to and including 7.1.0, and TIBCO Jaspersoft Reporting and Analytics for AWS: versions up to and including 7.1.0.

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 (stored) cross-site scripting vulnerability exists in the repository component of TIBCO JasperReports Server and related products (Community Edition, for ActiveMatrix BPM, and AWS variants). Attackers can inject malicious scripts into the repository that are stored on the server and executed when other users view or interact with the compromised content.

MitigationApply vendor patches to upgrade to a fixed version beyond 7.1.0, or implement server-side input validation and output encoding on the repository component to neutralize malicious script payloads.

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.3.4<= 6.4.3<= 7.1.0= 6.4.0= 6.4.1= 6.4.2= 6.4.3= 7.1.0
JaspersoftApplication
Affected:<= 7.1.0
Jaspersoft Reporting And AnalyticsApplication
Affected:<= 7.1.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 JasperReports Server version
    Log into the web interface and navigate to the Help > About page, or check the build.properties or version files in the installation directory (typically in <install_dir>/build.xml or <install_dir>/reportserver/build.properties)
    Affected if The installed version is 6.3.4 or lower, 6.4.0 through 6.4.3, or 7.1.0 or lower (all <= 7.1.0)
  2. Confirm repository component is enabled
    Verify the repository service is running and accessible by logging into the web UI and attempting to browse the repository tree (typically under the 'View' > 'Repository' menu or the 'Repository' sidebar panel)
    Affected if The repository component is accessible to users without administrator privileges, allowing file and content uploads
  3. Inspect repository content for suspicious scripts
    Using the web UI, navigate through repository folders and inspect any stored reports, images, or content files. Alternatively, query the database tables (typically JIReportJob or similar repository tables) for HTML script tags, javascript: URIs, or event handler attributes
    Affected if Any repository content contains unencoded <script>, <img src=javascript:>, onload=, onerror=, or similar XSS vectors
  4. Review web access logs for XSS attack patterns
    Examine the application server access logs (typically in <install_dir>/apache-tomcat/logs or similar) for repeated requests containing script tags or event handlers in repository-related URLs
    Affected if Logs show incoming requests with malicious script payloads being stored in repository fields

You are affected if your JasperReports Server or Jaspersoft installation is version 7.1.0 or lower and the repository component is exposed to users without server-side input validation.

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 7.1.0
Interim mitigation

Apply vendor patches to upgrade to a fixed version beyond 7.1.0, or implement server-side input validation and output encoding on the repository component to neutralize malicious script payloads.

Fix this in Jasperreports Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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