dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2018-5431

MEDIUM · 5.4 CVSS v3.0 Published 2018-04-17
Fix available
A fix is available. Upgrade to after 6.4.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 domain designer component 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 contains a vulnerability which may allow, in the context of a non-default permissions configuration, persisted cross-site scripting (XSS) attacks. 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 · high confidence

A stored cross-site scripting (XSS) vulnerability exists in the domain designer component of TIBCO JasperReports Server and related products. The vulnerability can be exploited in non-default permission configurations, allowing attackers to inject malicious scripts that persist within the system.

MitigationApply vendor patches when available; until then, restrict domain designer permissions to minimize attack surface and implement strict input validation on all user-supplied content.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 installed JasperReports Server version
    Access the server admin interface or check the product about page. Typically found in: Manage > Server Settings > About, or by inspecting the jasperreports-server-build.properties file in the installation directory.
    Affected if The installed version matches <= 6.2.4, 6.3.0, 6.3.2, 6.3.3, 6.4.0, 6.4.2, or any version <= 6.4.2.
  2. Confirm Jaspersoft product variant
    Identify whether the installation is JasperReports Server, Jaspersoft, or Jaspersoft Reporting And Analytics. Check the product name displayed in the admin UI or installation metadata.
    Affected if The product is any of the three listed affected products and the version is <= 6.4.2.
  3. Verify domain designer component is accessible
    Check if the Domain Designer feature is enabled and accessible within the installation. This is typically found under: Create > Domain, or in the Ad Hoc Views section where users can design domains.
    Affected if The domain designer component is present and accessible to users.
  4. Inspect domain designer permission configurations
    Review the permission settings for domain designer. Navigate to: Manage > Roles and Permissions, or the domain security settings. Look for any non-default permission grants to standard or non-standard users.
    Affected if Non-default permissions have been configured for the domain designer, granting elevated or unusual access to users who would not have it by default.
  5. Search for suspicious stored content in domains
    Review any custom domains created via domain designer. Check the domain schema, calculated fields, and display names for any unexpected script tags, javascript: URIs, or HTML elements that may indicate injected XSS payloads.
    Affected if Any stored XSS payloads are found within domain definitions, particularly in field names, descriptions, or calculated expressions.

A user is affected if they are running any of the listed product versions (JasperReports Server <= 6.4.2, Jaspersoft <= 6.4.2, or Jaspersoft Reporting And Analytics <= 6.4.2) AND the domain designer component is accessible with non-default permissions configured.

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.

From vendor data
Upgrade available Upgrade to a release after 6.4.2
Interim mitigation

Apply vendor patches when available; until then, restrict domain designer permissions to minimize attack surface and implement strict input validation on all user-supplied content.

Fix this in Jasperreports Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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