dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2022-22773

MEDIUM · 5.4 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to 8.0.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 REST API component of TIBCO Software Inc.'s 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 difficult to exploit Reflected Cross Site Scripting (XSS) vulnerabilities that allow a low privileged attacker with network access to execute scripts targeting the affected system or the victim's local system. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Server: versions 8.0.1 and below, TIBCO JasperReports Server - Community Edition: versions 8.0.1 and below, TIBCO JasperReports Server - Developer Edition: versions 8.0.0 and below, TIBCO JasperReports Server for AWS Marketplace: versions 8.0.1 and below, TIBCO JasperReports Server for ActiveMatrix BPM: versions 7.9.2 and below, and TIBCO JasperReports Server for Microsoft Azure: versions 8.0.1 and below.

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

TIBCO JasperReports Server contains a reflected Cross-Site Scripting (XSS) vulnerability in its REST API component. The vulnerability is described as difficult to exploit and allows a low-privileged attacker with network access to execute malicious scripts targeting the affected system or victim's local system.

MitigationApply vendor-provided patches or upgrade to a fixed version of TIBCO JasperReports Server. Additionally, implement input validation and output encoding on REST API endpoints to mitigate XSS vectors.

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.9.2< 8.0.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.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 installed TIBCO JasperReports Server version
    Locate the version information through the product's web interface (typically via Help > About) or check version files in the installation directory
    Affected if The installed version is 7.9.2 or lower, or is 8.0.0 or 8.0.1 (any version below 8.0.2)
  2. Verify REST API component accessibility
    Confirm the REST API endpoint is exposed by accessing the JasperReports Server REST services URL (commonly /jasperserver-pro/rest/)
    Affected if The REST API is accessible over the network without additional authentication controls beyond standard login
  3. Confirm low-privileged user access
    Verify that low-privileged users (non-admin accounts) have network access to the JasperReports Server instance
    Affected if Low-privileged authenticated users can make REST API requests to the server

A user is affected if their TIBCO JasperReports Server version is 7.9.2 or lower, or falls between 8.0.0 and 8.0.1 inclusive, and the REST API component is exposed to network access.

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 8.0.2 or later
Fixed in 8.0.2
Interim mitigation

Apply vendor-provided patches or upgrade to a fixed version of TIBCO JasperReports Server. Additionally, implement input validation and output encoding on REST API endpoints to mitigate XSS vectors.

Recommended fix High confidence

TIBCO JasperReports Server 8.0.2 or later (including Community Edition, Developer Edition, AWS Marketplace, ActiveMatrix BPM, and Microsoft Azure variants)

  1. 1. Identify the current installed version of TIBCO JasperReports Server using the administration console or server logs
  2. 2. Review the TIBCO JasperReports Server upgrade documentation for your specific deployment type
  3. 3. Create a full backup of the JasperReports Server database, configuration files, and repository data
  4. 4. Stop the JasperReports Server application services
  5. 5. If running in a clustered environment, disable all nodes except the one being upgraded
  6. 6. Run the TIBCO JasperReports Server installer for version 8.0.2 or later
  7. 7. After installation, verify that all database connections and repository configurations are intact
  8. 8. Start the JasperReports Server services and verify the application initializes correctly
Caveat Minor: Review release notes for any deprecated features or configuration changes between 7.x/8.0.x to 8.0.2; test custom reports and integrations in a non-production environment first

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

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