dbcve.org
Jasperreports LibraryApplication · Tibco

CVE-2022-22771

HIGH · 8.8 CVSS v3.1 Published 2022-03-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Server component of TIBCO Software Inc.'s TIBCO JasperReports Library, TIBCO JasperReports Library for ActiveMatrix BPM, TIBCO JasperReports Server, TIBCO JasperReports Server for AWS Marketplace, TIBCO JasperReports Server for ActiveMatrix BPM, and TIBCO JasperReports Server for Microsoft Azure contains a directory-traversal vulnerability that may theoretically allow web server users to access contents of the host system. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Library: version 7.9.0, TIBCO JasperReports Library for ActiveMatrix BPM: version 7.9.0, TIBCO JasperReports Server: versions 7.9.0 and 7.9.1, TIBCO JasperReports Server for AWS Marketplace: versions 7.9.0 and 7.9.1, TIBCO JasperReports Server for ActiveMatrix BPM: versions 7.9.0 and 7.9.1, and TIBCO JasperReports Server for Microsoft Azure: version 7.9.1.

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 directory traversal vulnerability in the Server component of TIBCO JasperReports that allows web server users to access contents of the host system by using '../' sequences to escape the web root directory. The vulnerability has a CVSS score of 8.8 (HIGH), indicating significant risk of unauthorized file access.

MitigationApply the vendor-released patches for the affected versions (7.9.0 and 7.9.1). If immediate patching is not possible, implement web application firewall rules to block traversal patterns and restrict file system permissions to limit exposure.

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 LibraryApplication
Affected:= 7.9.0
Jasperreports ServerApplication
Affected:= 7.9.0= 7.9.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 JasperReports installation and version
    Locate the JasperReports Server installation directory and check the version manifest or version file (typically in the installation root or a VERSION file). Alternatively, log into the JasperReports Server web UI and navigate to the About or Administration section to view the installed version.
    Affected if The installed version matches 7.9.0 or 7.9.1 for the Server component, or 7.9.0 for the Library component.
  2. Confirm Server component is running
    Check if the JasperReports Server web application is running by accessing the web interface URL (typically http://localhost:8080/jasperserver or similar) or by checking running processes/ services for the JasperReports Server process.
    Affected if The Server component is actively running and accessible via HTTP/HTTPS.
  3. Verify web root directory structure
    Inspect the web application deployment directory (typically under the deploy or webapp folder within the JasperReports installation) to confirm the web root structure exists and is accessible.
    Affected if The web root directory is present and the Server component is configured to serve web requests.
  4. Test for directory traversal exposure
    Send a test HTTP request to the Server endpoint using a path with '../' sequences (for example: GET /jasperserver/../../../../etc/passwd or similar traversal pattern) to verify whether the vulnerability is present. This should only be done in authorized test environments.
    Affected if The server responds with file contents outside the intended web root directory, indicating the traversal vulnerability is exploitable.

A user is affected if they are running JasperReports Server version 7.9.0 or 7.9.1 (or JasperReports Library 7.9.0) with the Server component exposed and accessible via web, and directory traversal patterns return files outside the web root.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-released patches for the affected versions (7.9.0 and 7.9.1). If immediate patching is not possible, implement web application firewall rules to block traversal patterns and restrict file system permissions to limit exposure.

Fix this in Jasperreports Library Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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