dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2022-41563

MEDIUM · 5.4 CVSS v3.1 Published 2022-12-13
Fix available
A fix is available. Upgrade to after 8.1.0 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 Dashboard component of TIBCO Software Inc.'s TIBCO JasperReports Server, TIBCO JasperReports Server, 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 low privileged attacker with network access to execute Stored Cross Site Scripting (XSS) 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 - 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 · moderate confidence

TIBCO JasperReports Server's Dashboard component contains a stored Cross-Site Scripting (XSS) vulnerability. A low-privileged attacker with network access can inject malicious scripts into the Dashboard that execute when other users interact with the compromised content. This is a persistent XSS since the malicious payload is stored on the server.

MitigationApply the vendor-supplied patch or upgrade to a fixed version beyond 8.1.0. Review the Dashboard component for unsanitized user input and implement proper output encoding.

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

CVSS:3.1/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 the installed JasperReports Server version
    Log into the web UI and navigate to the About page (typically at /jasperserver/abc versions), or check the version.properties file in the installation directory. You can also examine the server startup logs for the version number.
    Affected if The installed version is 8.0.2 or lower, or exactly 8.1.0.
  2. Confirm the Dashboard component is accessible
    Verify that the Dashboard functionality is available in the JasperReports Server installation by logging in and attempting to access the Dashboard creation or viewing interface.
    Affected if The Dashboard component is present and functional in the environment.
  3. Review Dashboard content for unauthorized scripts
    As an administrator, use the Dashboard management interface or database queries on the repository tables to inspect saved Dashboards for any script tags, javascript: URIs, or event handler attributes (onclick, onerror, etc.) that may indicate injected malicious code.
    Affected if Any Dashboard contains suspicious script content that was not authored by authorized administrators.
  4. Check server access logs for XSS attack patterns
    Review the JasperReports Server access logs for repeated requests containing script tags or encoded XSS payloads targeting the Dashboard endpoint.
    Affected if Log analysis reveals injection attempts with malicious scripts directed at Dashboard functionality.

You are affected if the installed JasperReports Server version is 8.0.2 or lower, or exactly 8.1.0, and the Dashboard component is enabled and accessible to users.

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

Apply the vendor-supplied patch or upgrade to a fixed version beyond 8.1.0. Review the Dashboard component for unsanitized user input and implement proper output encoding.

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-41563 — 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-41563 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