CriticalCVE-2018-5430

    TIBCO JasperReports Server Information Disclosure Vulnerability (CVE-2018-5430)

    Published In CISA KEV since Sources: CVE.org

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • TIBCO JasperReports Server lte *..6.2.4
    • TIBCO JasperReports Server eq 6.3.0..6.3.0
    • TIBCO JasperReports Server eq 6.3.2..6.3.2
    • TIBCO JasperReports Server eq 6.3.3..6.3.3
    • TIBCO JasperReports Server eq 6.4.0..6.4.0
    • TIBCO JasperReports Server eq 6.4.2..6.4.2
    • TIBCO JasperReports Server Community Edition lte *..6.4.2
    • TIBCO JasperReports Server for ActiveMatrix BPM lte *..6.4.2
    • TIBCO Jaspersoft for AWS with Multi-Tenancy lte *..6.4.2
    • TIBCO Jaspersoft Reporting and Analytics for AWS lte *..6.4.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.7

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org

    48.1 %

    EPSS score

    Elevated — model estimates 10-50% exploitation likelihood.

    Source: FIRST EPSS, percentile 98.9

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    216.67 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.7
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    48.1 %
    Elevated — model estimates 10-50% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    98.9
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 7 February 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-200

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This CVE sits on KEV because, despite requiring authentication, the practical bar is near zero: JasperReports deployments routinely ship with default accounts, open self-registration and broadly assigned ROLE_USER, while the leaked config files typically contain database, LDAP and mail credentials that enable immediate lateral movement. Exploitation likelihood is rated very high and the CVSS profile (network-reachable, low complexity, high impact on confidentiality, integrity and availability) is severe — treat every internet- or partner-exposed instance as P1 and purely internal BI servers as P2. It is not flagged as a ransomware vector, but it is a credible credential-harvesting step in multi-stage intrusions targeting BI and data-warehouse infrastructure.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Apply the vendor patch: upgrade JasperReports Server to 6.4.3 / 7.1 or later per TIBCO advisory 2018-004. The same minimum version applies to Community Edition and the ActiveMatrix BPM variant; refresh the AWS Marketplace images for Jaspersoft for AWS (Multi-Tenancy) and Reporting and Analytics for AWS.
      • Exposure sweep: inventory every JasperReports instance (internal BI portals, tenant URLs, embedded dashboards), prioritising anything reachable from the internet or partner networks. Place directly exposed instances behind a reverse proxy, VPN or ZTNA until patched.
      • Account hygiene: because any authenticated user can trigger the flaw — including self-registered users and defaults such as jasperadmin, joeuser, demo — rotate default passwords, disable demo accounts, and switch off self-registration (js.config.properties, registration workflow).
      • Treat configuration files as compromised: js.jdbc.properties, js.config.properties, jasperserver.properties, keystores. Rotate database credentials, LDAP bind credentials, API keys and encryption keys if the instance was reachable prior to patching.
      • Review web access logs for the last 24 months (where retained) for suspicious Spring Webflow requests (see detection section) and raise an incident ticket on hits.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: place JasperReports in a dedicated BI VLAN, allow ingress only via reverse proxy (nginx/Apache/F5), restrict admin access to a jump host. Block direct user-network reach to ports 8080/8443.
      • WAF rule: filter Spring Webflow requests with suspicious _eventId/execution parameters; block path components containing .., URL-encoded slashes (%2f, %252f) and references to WEB-INF/, META-INF/, .properties, .xml inside Webflow contexts.
      • IAM hardening: strip ROLE_USER to the minimum required privileges, remove or lock default accounts, enforce LDAP/SAML authentication over the internal user DB, and front the proxy with MFA.
      • Filesystem hardening: restrict the Tomcat runtime user (jasperserver) to read-only on config files; encrypt sensitive property files with the JCE keystore mechanism that JasperReports supports for DB credentials.
      • Configuration monitoring: enable FIM (Wazuh, Tripwire) on WEB-INF/ and apache-tomcat/webapps/jasperserver/WEB-INF/; any read anomaly by the Tomcat process is an incident.
      • Compensating control when patching is blocked: constrain the reverse proxy to an allow-list of required URL paths (/rest_v2/, specific /flow.html flows) and return HTTP 403 for everything else.

    3. Runbook step 3

      Detection rules

      • Web access log (Tomcat/nginx): pattern match GET/POST against Spring Webflow URLs returning Content-Type: application/octet-stream or response size > 10 KB on atypical flow endpoints. Sigma shape: selection: cs-uri-stem|contains: ['/flow.html', '/WEB-INF', '/jasperserver/', '.properties'].
      • Suricata/Zeek: HTTP requests whose URI contains WEB-INF, js.jdbc.properties or js.config.properties as high-severity alerts — alert http any any -> $JASPER_SERVERS any (msg:"JasperReports config file access CVE-2018-5430"; content:"js.jdbc.properties"; http_uri; sid:1000543;).
      • Sysmon EID 1 / Linux auditd: Tomcat/Java process (catalina.sh, java) opening config files unusually often outside startup — auditd rule: -w /opt/jasperreports/apache-tomcat/webapps/jasperserver/WEB-INF/ -p r -k jasper_config_read.
      • SIEM correlation (KQL snippet): WebServerLogs | where UrlPath has_any ("flow.html","webflow") | where ResponseSize > 10000 or UrlPath has_any (".properties",".xml","WEB-INF") | summarize count() by SourceIP, UserName | where count_ > 5.
      • Behavioural baseline: a low-privilege user (ROLE_USER) hitting > 20 distinct flow endpoints in a short window, or triggering downloads with atypical MIME types, is a credible exploitation signal.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    TIBCO Software Inc.TIBCO JasperReports Server
    • 6.4.2
    • ≤ 6.2.4
    • 6.3.0
    • 6.3.3
    • 6.3.2
    • 6.4.0
    • —
    • —
    • —
    • —
    • —
    • —
    TIBCO Software Inc.TIBCO JasperReports Server Community Edition
    • ≤ 6.4.2
    • —
    TIBCO Software Inc.TIBCO JasperReports Server for ActiveMatrix BPM
    • ≤ 6.4.2
    • —
    TIBCO Software Inc.TIBCO Jaspersoft for AWS with Multi-Tenancy
    • ≤ 6.4.2
    • —
    TIBCO Software Inc.TIBCO Jaspersoft Reporting and Analytics for AWS
    • ≤ 6.4.2
    • —
    tibcojasperreports_server
    • ≤ 6.4.2
    • 6.4.0
    • 6.3.0
    • 6.3.3
    • 6.4.2
    • 6.3.2
    • ≤ 6.2.4
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    tibcojaspersoft
    • ≤ 6.4.2
    • —
    tibcojaspersoft_reporting_and_analytics
    • ≤ 6.4.2
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-200Exposure of Sensitive Information to an Unauthorized Actor

      Class

      The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

      Entry at MITRE CWE-200

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    Exploit-DBEDB-ID 44623 (opens in a new tab)exploit-db.comPoC (publicly reported)reported, not verified—

    References & sources

    • exploit-db.com44623Exploit, x_refsource_EXPLOIT-DB, Exploit, Third-party advisory, Vulnerability database
    • rhinosecuritylabs.comapplication-security/authenticated-file-read-vulnerability-in-j…x_refsource_MISC, Exploit, Third-party advisory
    • tibco.comsupport/advisories/2018/04/tibco-security-advisory-april-17-201…x_refsource_CONFIRM, Broken link, Vendor advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2018-5430government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2018-5430
    <a href="https://intel.neosec.eu/en/cve/CVE-2018-5430"><img src="https://intel.neosec.eu/badge/cve/CVE-2018-5430.svg?lang=en" alt="CVE-2018-5430 – NEOSEC Intel" height="20"></a>