dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 19 Jan 2023.
Jasperreports LibraryApplication · Tibco

CVE-2018-18809

MEDIUM · 6.5 CVSS v3.1 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
In the wild High EPSS Public exploit 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
The default server implementation of TIBCO Software Inc.'s TIBCO JasperReports Library, TIBCO JasperReports Library Community Edition, TIBCO JasperReports Library for ActiveMatrix BPM, 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 directory-traversal vulnerability that may theoretically allow web server users to access contents of the host system. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Library: versions up to and including 6.3.4; 6.4.1; 6.4.2; 6.4.21; 7.1.0; 7.2.0, TIBCO JasperReports Library Community Edition: versions up to and including 6.7.0, TIBCO JasperReports Library for ActiveMatrix BPM: versions up to and including 6.4.21, 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 6.4.3; 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, 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

Directory traversal vulnerability in the default server implementation of TIBCO JasperReports allows remote attackers to use traversal sequences (e.g., ../) to access files outside the web root, potentially exposing sensitive host system files. The flaw affects both the Library and Server components across multiple product editions.

MitigationApply vendor-supplied patches for affected versions (6.x through 7.2.0). If immediate patching is not feasible, restrict network access to JasperReports server endpoints and implement web application firewall rules to block directory traversal patterns.

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 LibraryApplication
Affected:<= 6.4.21<= 6.7.0= 7.1.0= 7.2.0
Jasperreports ServerApplication
Affected:<= 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/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 installation
    Locate JasperReports Server or Library installations by checking for common installation directories (e.g., /opt/tibco, C:\Program Files\TIBCO, or application deployment directories) and look for jasperreports*.jar files or jasperreports-server directory.
    Affected if JasperReports Server or Library is installed on the system
  2. Determine installed version
    For Server installations, check version.txt or about page in the web interface. For Library, inspect the jasperreports-x.x.x.jar filename or examine the MANIFEST.MF file within the JAR.
    Affected if Version matches <= 6.4.21, <= 6.7.0, 7.1.0, 7.2.0 for Library or <= 6.4.3, 7.1.0 for Server, or any version <= 7.1.0 for Jaspersoft/Jaspersoft Reporting And Analytics
  3. Confirm default server is enabled
    Check if the JasperReports web application is deployed and running by examining application server configurations (Tomcat, JBoss, etc.) for jasperreports-server or jasperreports war deployments, or by accessing the typical web endpoints (commonly /jasperserver/, /jasperserver-pro/, or /reports/).
    Affected if The default JasperReports web server interface is deployed and accessible
  4. Verify network accessibility
    Check if the JasperReports web port (default 8080 for Tomcat, 80/443 for IIS, or configured ports) is exposed to network segments beyond localhost by reviewing firewall rules, reverse proxy configurations, or load balancer settings.
    Affected if The JasperReports web interface is reachable from network locations rather than localhost only

A user is affected if they have a vulnerable version (as listed above) with the default JasperReports server/web interface enabled and exposed to network access.

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-supplied patches for affected versions (6.x through 7.2.0). If immediate patching is not feasible, restrict network access to JasperReports server endpoints and implement web application firewall rules to block directory traversal patterns.

Recommended fix Moderate confidence

TIBCO JasperReports Library: 6.4.22 or later / 7.3.0 or later; TIBCO JasperReports Server: 7.1.1 or later; TIBCO Jaspersoft products: 7.2.0 or later

  1. 1. Identify the exact installed version of TIBCO JasperReports product (Library, Server, or Jaspersoft) by checking the product's about or version information.
  2. 2. Based on the product type, upgrade to a fixed release: For TIBCO JasperReports Library, upgrade to version 6.4.22 or later, or 7.3.0 or later. For TIBCO JasperReports Server, upgrade to version 7.1.1 or later. For TIBCO Jaspersoft for AWS and TIBCO Jaspersoft Reporting and Analytics for AWS, upgrade to version 7.2.0 or later.
  3. 3. After upgrading, verify the installation by checking the product version and testing the web interface.
  4. 4. Validate that the directory traversal vulnerability is patched by attempting a controlled test of path traversal (with proper authorization and in a test environment only).
Caveat Review TIBCO release notes for the target version to check for any breaking changes or required migration steps, especially when upgrading across major version jumps (e.g., from 6.x to 7.x).

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

Fix this in Jasperreports Library Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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