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 ServerApplication · Tibco

CVE-2018-5430

HIGH · 8.8 CVSS v3.1 Published 2018-04-17
Fix available
A fix is available. Upgrade to after 6.4.2 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 Spring web flows 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 contain a vulnerability which may allow any authenticated user read-only access to the contents of the web application, including key configuration files. Affected releases include TIBCO Software Inc.'s TIBCO JasperReports Server: versions up to and including 6.2.4; 6.3.0; 6.3.2; 6.3.3;6.4.0; 6.4.2, TIBCO JasperReports Server Community Edition: versions up to and including 6.4.2, TIBCO JasperReports Server for ActiveMatrix BPM: versions up to and including 6.4.2, TIBCO Jaspersoft for AWS with Multi-Tenancy: versions up to and including 6.4.2, TIBCO Jaspersoft Reporting and Analytics for AWS: versions up to and including 6.4.2.

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

Spring web flow vulnerability in TIBCO JasperReports Server allows any authenticated user to gain unauthorized read-only access to web application contents, including sensitive configuration files. This is a privilege escalation/authorization bypass issue where the web flow fails to properly restrict file system access based on user roles.

MitigationApply vendor-supplied patches or upgrade to a fixed version beyond 6.4.2. Restrict network access to the JasperReports Server interface until the patch can be applied.

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.4<= 6.4.2= 6.3.0= 6.3.2= 6.3.3= 6.4.0= 6.4.2
JaspersoftApplication
Affected:<= 6.4.2
Jaspersoft Reporting And AnalyticsApplication
Affected:<= 6.4.2

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 TIBCO JasperReports product installation
    Locate the JasperReports Server installation directory. Common paths include: /opt/jasperreports-server, C:\Program Files\TIBCO\JasperReports Server, or /installs/jasperreports-server. Check for the presence of jasperreports-server.ear or war directories, and look for build.xml or version.properties files in the installation root.
    Affected if The product is TIBCO JasperReports Server, Jaspersoft, or Jaspersoft Reporting And Analytics installed on the system.
  2. Determine installed version
    Open the version file in the installation directory. Common locations: <install>/build/version.properties, <install>/build.xml (contains version property), or check the About page in the web application admin console at /jasperserver-pro/assertionServlet?getVersion=true or /jasperserver/assertionServlet?getVersion=true
    Affected if The installed version is <= 6.2.4, = 6.3.0, = 6.3.2, = 6.3.3, = 6.4.0, = 6.4.2, or <= 6.4.2 for Jaspersoft variants.
  3. Verify web flow module is enabled
    Inspect the web application configuration files. Check WEB-INF/web.xml for org.springframework.web.flow.servlet.FlowDispatcherServlet or similar Spring Web Flow servlet mappings. Also check WEB-INF/flows/ directory exists within the jasperreports-server war deployment.
    Affected if The Spring Web Flow dispatcher servlet is registered and the flow configuration directory is present, which is the default configuration for JasperReports Server.
  4. Confirm user authentication layer is accessible
    Test access to the login page at /jasperserver/login.html or /jasperserver-pro/login.html. Verify that user authentication is functional and that authenticated sessions can be established.
    Affected if The web application accepts authentication and allows logged-in user sessions, which is required for exploitation of this vulnerability.

A user is affected if they run any TIBCO JasperReports Server, Jaspersoft, or Jaspersoft Reporting And Analytics version <= 6.2.4, 6.3.0, 6.3.2, 6.3.3, 6.4.0, 6.4.2, or <= 6.4.2 where Spring Web Flow handles requests and authenticated users can access the application.

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

Apply vendor-supplied patches or upgrade to a fixed version beyond 6.4.2. Restrict network access to the JasperReports Server interface until the patch can be applied.

Recommended fix Moderate confidence

TIBCO JasperReports Server 7.x or later (versions beyond 6.4.2)

  1. 1. Identify the current installed version of TIBCO JasperReports Server or Jaspersoft by checking the application or administration console.
  2. 2. Take a complete backup of the JasperReports Server database and configuration files before proceeding with the upgrade.
  3. 3. Review TIBCO's official upgrade documentation for your specific deployment type (standalone, AWS, etc.).
  4. 4. Download the latest stable version of TIBCO JasperReports Server from the official TIBCO website (typically versions 7.x or later).
  5. 5. Execute the upgrade following TIBCO's standard upgrade procedure for your deployment model.
  6. 6. Verify the upgrade was successful by logging into the web interface and confirming all services are running.
  7. 7. Test that the path traversal vulnerability is no longer exploitable by attempting to access files outside the web root using the documented attack vector.
Caveat Major version upgrades from 6.x to 7.x may introduce configuration changes, API modifications, or database schema updates that require thorough testing in a non-production environment before deployment.

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

Fix this in Jasperreports Server Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,500
Get it fixed fast

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-5430 — 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-5430 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