dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2021-35496

HIGH · 7.5 CVSS v3.1 Published 2021-10-12
Fix available
A fix is available. Upgrade to after 7.9.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 XMLA Connections component of TIBCO Software Inc.'s TIBCO JasperReports Server, TIBCO JasperReports Server, TIBCO JasperReports Server, TIBCO JasperReports Server, TIBCO JasperReports Server - Community Edition, TIBCO JasperReports Server - Developer Edition, TIBCO JasperReports Server for AWS Marketplace, TIBCO JasperReports Server for ActiveMatrix BPM, and TIBCO JasperReports Server for Microsoft Azure contains a difficult to exploit vulnerability that allows a low privileged attacker with network access to interfere with XML processing in the affected component. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Server: versions 7.2.1 and below, TIBCO JasperReports Server: versions 7.5.0 and 7.5.1, TIBCO JasperReports Server: version 7.8.0, TIBCO JasperReports Server: version 7.9.0, TIBCO JasperReports Server - Community Edition: versions 7.8.0 and below, TIBCO JasperReports Server - Developer Edition: versions 7.9.0 and below, TIBCO JasperReports Server for AWS Marketplace: versions 7.9.0 and below, TIBCO JasperReports Server for ActiveMatrix BPM: versions 7.9.0 and below, and TIBCO JasperReports Server for Microsoft Azure: version 7.8.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

The vulnerability exists in the XMLA (XML for Analysis) Connections component of TIBCO JasperReports Server. It allows a low-privileged attacker with network access to interfere with XML processing, likely through an XXE (XML External Entity) injection or similar XML parsing flaw. The attack is described as difficult to exploit but achievable.

MitigationApply vendor-provided patches for CVE-2021-35496 by upgrading to a patched version of TIBCO JasperReports Server, or disable XMLA Connections if not required in the environment.

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:<= 7.2.1<= 7.8.0<= 7.9.0= 7.5.0= 7.5.1= 7.8.0= 7.9.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.1/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 the installed JasperReports Server version
    Log into the JasperReports Server admin console (JasperServer) and navigate to the About or Server Information page, or check the version manifest file (typically in the installation directory under ../buildomatic or in the WAR file metadata
    Affected if The installed version is 7.5.0, 7.5.1, 7.8.0, 7.9.0, or any version <= 7.2.1, <= 7.8.0, or <= 7.9.0
  2. Locate the XMLA Connections configuration
    Check the JasperReports Server configuration files for XMLA settings. Look in the default master.properties or xmla-datasource-config.xml files typically found in the ../WEB-INF directory of the JasperReports Server installation
    Affected if XMLA Connections are explicitly configured or enabled in the configuration files (the vulnerability exists in this component)
  3. Verify if the XMLA web service endpoint is accessible
    Check network accessibility of the XMLA endpoint by reviewing the server's web.xml for the XMLA servlet mapping, typically exposed at a path like /xmla or /XMLA, and confirm the server is listening on accessible network interfaces
    Affected if The XMLA endpoint is reachable over the network (even on localhost, the vulnerability still exists in the XML processing)
  4. Confirm low-privileged user access exists
    Review user roles and permissions in the JasperReports Server admin console to determine if any non-administrator accounts exist with basic login access
    Affected if Any low-privileged user accounts exist that can authenticate to the server (the CVE states a low-privileged attacker can exploit this)

The environment is affected if the installed JasperReports Server version falls within 7.5.0 through 7.9.0 (including 7.2.1 or earlier) AND the XMLA Connections component is enabled and accessible, regardless of whether low-privileged users currently exist.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.9.0
Interim mitigation

Apply vendor-provided patches for CVE-2021-35496 by upgrading to a patched version of TIBCO JasperReports Server, or disable XMLA Connections if not required in the environment.

Recommended fix Moderate confidence

TIBCO JasperReports Server version 7.9.0 or later (contact TIBCO for the exact fixed release)

  1. Check the current installed version of TIBCO JasperReports Server using the administration console or server logs
  2. Contact TIBCO support or visit the official TIBCO support portal to obtain the specific patch or updated version that addresses CVE-2021-35496
  3. Review the TIBCO JasperReports Server release notes for version 7.9.0 or later to confirm the security fix for the XXE vulnerability is included
  4. Plan the upgrade during a maintenance window to minimize business impact
  5. Backup the current JasperReports Server database and configuration files before proceeding with the upgrade
  6. Execute the upgrade following the official TIBCO upgrade documentation for your specific edition
  7. After upgrade, verify the XMLA Connections component is functioning correctly and the vulnerability is resolved by reviewing server logs and testing XML processing functionality
Caveat Review TIBCO release notes for your specific edition version to identify any breaking changes or required migration steps before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jasperreports Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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