dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2022-41562

HIGH · 8.4 CVSS v3.1 Published 2022-12-13
Fix available
A fix is available. Upgrade to after 8.1.0 or later.
See remediation →
88/100
Remediation priority · High
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 HTML escaping component of TIBCO Software Inc.'s 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 AWS Marketplace, TIBCO JasperReports Server for Microsoft Azure, and TIBCO JasperReports Server for Microsoft Azure contains an easily exploitable vulnerability that allows a privileged/administrative attacker with network access to execute an XSS attack on the affected system. A successful attack using this vulnerability requires human interaction from a person other than the attacker. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Server: versions 8.0.2 and below, TIBCO JasperReports Server: version 8.1.0, TIBCO JasperReports Server - Community Edition: versions 8.1.0 and below, TIBCO JasperReports Server - Developer Edition: versions 8.1.0 and below, TIBCO JasperReports Server for AWS Marketplace: versions 8.0.2 and below, TIBCO JasperReports Server for AWS Marketplace: version 8.1.0, TIBCO JasperReports Server for Microsoft Azure: versions 8.0.2 and below, and TIBCO JasperReports Server for Microsoft Azure: version 8.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

This is a stored Cross-Site Scripting (XSS) vulnerability in the HTML escaping component of TIBCO JasperReports Server. A privileged/administrative attacker can inject malicious scripts through unsanitized input that gets rendered in HTML without proper escaping. The attack requires human interaction (e.g., an admin viewing injected content), making it exploitable but not fully automated.

MitigationUpgrade to a patched version of TIBCO JasperReports Server (contact TIBCO for specific patches). Until then, implement strict input validation and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

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:<= 8.0.2<= 8.1.0= 8.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
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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
    Access the administration interface and navigate to the About page, or check the build.properties/version.xml file in the JasperReports Server installation directory under the webapp folder
    Affected if The version is 8.0.2 or lower, or 8.1.0 (any version <= 8.0.2, or = 8.1.0, or <= 8.1.0 that is not patched)
  2. Locate HTML escaping component
    Inspect the JasperReports Server web application files, specifically looking for the HTML escaping or sanitizer libraries in the WEB-INF/lib directory of the deployed JasperReports application
    Affected if The component is present and being used by the application for rendering user-supplied content in HTML contexts
  3. Identify input vectors that use HTML escaping
    Review the application's input handling code or test by submitting HTML/JavaScript payloads through report parameters, report titles, dashboard widgets, or other user-definable text fields in the web interface
    Affected if The application accepts HTML input and renders it without proper encoding in the response (evidence of unsanitized output)
  4. Confirm privileged access exists
    Verify if any user accounts with administrative or privileged roles exist in the system, as the attack requires a privileged attacker to inject the malicious script
    Affected if There are administrative or privileged user accounts that can access input fields used by the vulnerable HTML escaping component

You are affected if your installed JasperReports Server version is 8.0.2 or lower, or exactly 8.1.0, and you have privileged users who can input content that gets rendered without HTML escaping in the application.

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

Upgrade to a patched version of TIBCO JasperReports Server (contact TIBCO for specific patches). Until then, implement strict input validation and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

Fix this in Jasperreports Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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