dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2018-18815

CRITICAL · 9.8 CVSS v3.0 Published 2019-03-07
Fix available
A fix is available. Upgrade to after 7.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The REST API 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, and TIBCO Jaspersoft Reporting and Analytics for AWS contains a vulnerability that theoretically allows unauthenticated users to bypass authorization checks for portions of the HTTP interface to the JasperReports Server. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Server: 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 · moderate confidence

A critical authorization bypass vulnerability exists in the REST API component of TIBCO JasperReports Server that theoretically allows unauthenticated attackers to bypass authorization checks for certain portions of the HTTP interface. This could enable unauthorized access to sensitive reporting functionality and data without proper authentication credentials.

MitigationApply vendor-provided patches or upgrade to a non-vulnerable version. If immediate patching is not feasible, implement strict network access controls and Web Application Firewall rules to limit exposure to the REST API endpoint.

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.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 if TIBCO JasperReports Server is installed
    Locate the JasperReports Server installation directory, typically under /opt/tibco/jasperreports-server or C:\Program Files\TIBS\jasperreports-server. Check for the presence of the jasperreports-server directory and its war deployment files.
    Affected if The product is present in the environment and the version falls within the affected ranges (6.4.0 through 6.4.3, 7.1.0, or any version <= 6.4.3 or <= 7.1.0).
  2. Determine the installed JasperReports Server version
    Locate the version file or check the build properties. The version is often visible in the administration console login page, in the WEB-INF/classes/jasperreports.properties file, or in a build.xml/build.properties file within the installation directory.
    Affected if The installed version matches 6.4.0, 6.4.1, 6.4.2, 6.4.3, 7.1.0 or falls at or below these versions in the 6.x or 7.x branches.
  3. Verify if the REST API component is enabled and accessible
    Check if the REST API servlet is mapped in the web.xml file (typically in WEB-INF/web.xml) under the path /rest or /rest_v2. Attempt to access an unauthenticated REST endpoint such as /jasperserver/rest/ or /jasperserver/rest_v2/ via HTTP request to confirm the endpoint responds.
    Affected if The REST API is accessible and responds without requiring authentication credentials.
  4. Confirm network exposure of the REST API endpoint
    Review network configuration, firewall rules, or reverse proxy settings to determine if the JasperReports Server and its REST API are exposed to untrusted networks or the public internet. Check the server.xml or standalone.xml for listener bindings.
    Affected if The REST API endpoint is reachable from networks outside the trusted internal environment without additional authentication barriers.

You are affected if TIBCO JasperReports Server (or Jaspersoft/Jaspersoft Reporting And Analytics) version 6.4.0-6.4.3 or 7.1.0 (or any version <= 7.1.0) is installed with the REST API component accessible without authentication, particularly from untrusted networks.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.1.0
Interim mitigation

Apply vendor-provided patches or upgrade to a non-vulnerable version. If immediate patching is not feasible, implement strict network access controls and Web Application Firewall rules to limit exposure to the REST API endpoint.

Recommended fix Moderate confidence

TIBCO JasperReports Server 7.1.1 or later stable release

  1. Identify the currently deployed JasperReports Server version using the administration console or system information
  2. Review TIBCO JasperReports Server release notes and security advisories for version 7.1.1 or later for security patches
  3. Upgrade JasperReports Server to version 7.1.1 or the latest stable release that includes the security fix
  4. After upgrading, verify that the REST API requires proper authentication and authorization by testing unauthenticated access attempts
  5. Confirm the fix by reviewing TIBCO Security Advisory (advisory ID: tibsa-2018-1025) for this specific vulnerability
Caveat Review release notes for potential configuration or compatibility changes between 7.1.0 and the target upgrade version; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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