CVE-2018-5430
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.
- CVSS
- 8.8High
- Exploited in the wild
- Yes, in CISA KEV since 29 Dec 2022CISA deadline for US federal agencies: 19 Jan 2023public exploit code
- EPSS
- 48.1%chance of exploitation in the next 30 daystop 2% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 17 Apr 2018analysed here 12 Nov 2026
Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)
Summary
Triage
- Attack surface
- Server-side
- Exploitable
- At runtime
- Attack vector
- network
- Can a WAF block it?
- Yes. See why
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| TIBCO Software Inc. TIBCO JasperReports Server | <= 6.2.46.3.06.3.26.3.36.4.06.4.2Vendor says fixed in: not stated | |
| TIBCO Software Inc. TIBCO JasperReports Server Community Edition | <= 6.4.2Vendor says fixed in: not stated | |
| TIBCO Software Inc. TIBCO JasperReports Server for ActiveMatrix BPM | <= 6.4.2Vendor says fixed in: not stated | |
| TIBCO Software Inc. TIBCO Jaspersoft for AWS with Multi-Tenancy | <= 6.4.2Vendor says fixed in: not stated | |
| TIBCO Software Inc. TIBCO Jaspersoft Reporting and Analytics for AWS | <= 6.4.2Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- tibco:jasperreports_server
- tibco:jaspersoft
- tibco:jaspersoft_reporting_and_analytics
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Yes. Path traversal sends `../` sequences in the request, which WAF rules catch, including the common encodings.
Also consider: canonical path validation · response filtering
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 29 Dec 2022.
- CISA due date
- 19 Jan 2023, the remediation deadline for US federal agencies
- CISA required action
- Apply updates per vendor instructions.
- Public exploit code
- Yes: 1 on Exploit-DB
- CISA SSVC
- exploitation active, automatable no, technical impact partialAssessed by CISA 7 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Exploit-DB
- JasperReports - (Authenticated) File Readwebapps, 3 May 2018
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 17 Apr 2018Published
- 3 May 2018First public exploit or proof of concept15 days later
- 29 Dec 2022Added to CISA KEV (exploited in the wild)1,701 days (about 5 years) later
- 19 Jan 2023CISA remediation due date (US federal agencies)21 days later
- 7 Feb 2025CISA SSVC assessment: exploitation active751 days (about 2 years) later
- 21 Oct 2025CVE record last updated256 days (about 9 months) later
- 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | LowThe attacker needs basic user privileges. | The attacker needs basic user privileges. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2018-5430 being exploited?
Yes. CVE-2018-5430 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2018-5430?
CVE-2018-5430 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2018-5430?
Yes. A fix has been recorded for CVE-2018-5430. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2018-5430 affect?
CVE-2018-5430 affects tibco:jasperreports_server, tibco:jaspersoft, tibco:jaspersoft_reporting_and_analytics. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
4 references in the CVE record, grouped by the tags the record gives them.
Exploits (1)
- exploit-db.com /exploits/44623/
Other links (3)
- rhinosecuritylabs.com /application-security/authenticated-file-read-vulnerability-in-jasperreports/
- tibco.com /support/advisories/2018/04/tibco-security-advisory-april-17-2018-tibco-jasperre
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-5430
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.