dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2018-18808

HIGH · 7.5 CVSS v3.0 Published 2019-03-07
Fix available
A fix is available. Upgrade to after 7.1.0 or later.
See remediation →
81/100
Remediation priority · High
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 domain management 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 race-condition vulnerability that may allow any users with domain save privileges to gain superuser privileges. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Server: versions up to and including 6.3.4; 6.4.0; 6.4.1; 6.4.2; 6.4.3; 7.1.0, TIBCO JasperReports Server Community Edition: versions up to and including 7.1.0, TIBCO JasperReports Server for ActiveMatrix BPM: versions up to and including 6.4.3, TIBCO Jaspersoft for AWS with Multi-Tenancy: versions up to and including 7.1.0, and TIBCO Jaspersoft Reporting and Analytics for AWS: versions up to and including 7.1.0.

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

Race condition vulnerability in the domain management component of TIBCO JasperReports Server allows any user with domain save privileges to gain superuser privileges by exploiting timing issues during domain save operations.

MitigationApply TIBCO vendor patches/upgrade to a fixed version beyond 7.1.0; review user permissions for domain save privileges until patched.

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.3.4<= 6.4.3<= 7.1.0= 6.4.0= 6.4.1= 6.4.2= 6.4.3= 7.1.0
JaspersoftApplication
Affected:<= 7.1.0
Jaspersoft Reporting And AnalyticsApplication
Affected:<= 7.1.0

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/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 installed JasperReports Server version
    Check the product version in the TIBCO JasperReports Server administration console, or look for version file in the installation directory (typically in a build.info or version.properties file)
    Affected if Installed version is 6.3.4 or lower, 6.4.0 through 6.4.3, or 7.1.0 or lower (including all 7.1.0 releases)
  2. Verify domain management component is in use
    Check if the Domain component feature is enabled and accessible in the JasperReports Server. This can be confirmed by logging into the web UI and looking for Domain or Domain Designer in the menu, or by checking for domain-related tables in the repository database
    Affected if Domain management feature exists in the installation and is accessible to users
  3. Identify users with domain save privileges
    Review user roles and permissions in the TIBCO JasperReports Server administration interface under 'Roles' or 'Permissions', specifically looking for any role that includes 'Domain Save' or 'Domain Create' capability
    Affected if Any user account is assigned a role that includes domain save or domain create permissions
  4. Check for superuser role assignment anomalies
    Audit the role assignments for all users, particularly checking if any user with domain save privileges also has superuser (administrator) role assignments that they should not possess
    Affected if Users with domain save privileges have unexpectedly been granted superuser or administrator roles beyond their original scope

You are affected if your installed JasperReports Server, Jaspersoft, or Jaspersoft Reporting And Analytics version falls within 6.3.4 or lower, 6.4.0-6.4.3, or 7.1.0 or lower AND any user account with domain save privileges exists in the system.

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

Apply TIBCO vendor patches/upgrade to a fixed version beyond 7.1.0; review user permissions for domain save privileges until patched.

Fix this in Jasperreports Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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