Threats / TIBCO / CVE-2018-5430
CVE-2018-5430
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
TIBCO JasperReports vulnerability
TIBCO JasperReports Server contains a path traversal vulnerability allowing authenticated users to read sensitive configuration files and web application contents.
Verdict
Today item — known-exploited.
An authenticated attacker can exploit CWE-22 path traversal to access restricted files including configuration data. This vulnerability has been observed in active exploitation and poses a moderate risk to confidentiality of sensitive system information.
CISA KEV Yes · 2022-12-295EPSS 0.48753 (verify live)6CVSS 7.73CISA SSVC Exploitation: active · Automatable: no · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-12-29).
Probability (EPSS)
EPSS 0.48753 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.7 (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) · Affected: TIBCO, JasperReports. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1717 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I authenticate to JasperReports Server using valid credentials.
Business
Legitimate user accounts exist across the organization with varying privilege levels.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft requests using path traversal sequences to bypass directory restrictions.
Business
Access controls fail to properly validate file paths requested by authenticated sessions.
3
Lateral reach — past segmentation narrative 3
Attacker
I read configuration files and application data outside my intended scope.
Business
Sensitive system settings, database credentials, and API keys are exposed to unauthorized disclosure.
4
Data at risk — exfiltration narrative 4
Attacker
I extract credentials and architectural details from retrieved files.
Business
Attackers gain intelligence to pivot to other systems or escalate privileges within the infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05