dbcve.org
Jasperreports ServerApplication · Tibco

CVE-2022-41561

HIGH · 7.2 CVSS v3.1 Published 2022-12-13
Fix available
A fix is available. Upgrade to after 8.1.0 or later.
See remediation →
78/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 JNDI Data Sources 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 Remote Code Execution to obtain a reverse shell on the affected system. 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

A JNDI Data Sources component vulnerability in TIBCO JasperReports Server allows a privileged attacker with network access to perform JNDI injection and achieve Remote Code Execution, enabling a reverse shell on the affected system.

MitigationUpgrade TIBCO JasperReports Server to a patched version (above 8.1.0) or apply vendor-provided patches; restrict administrative access and network exposure while awaiting remediation.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 installed JasperReports Server version
    Locate the JasperReports Server installation directory and check the version file or use the admin console to determine the exact version number
    Affected if The installed version is 8.0.2 or lower, or version 8.1.0 exactly (versions <= 8.0.2 or = 8.1.0 are affected)
  2. Verify JNDI Data Sources feature is configured
    Access the JasperReports Server admin interface and navigate to the Data Sources configuration section to determine if JNDI data sources are created and enabled
    Affected if A JNDI Data Source is defined and active in the JasperReports Server configuration
  3. Confirm network accessibility of admin interface
    Check if the JasperReports Server web interface (typically ports 8080 or 8443) is exposed to network segments accessible to untrusted users or external networks
    Affected if The admin interface is reachable from untrusted network locations, enabling remote attackers to trigger the JNDI injection
  4. Review audit logs for JNDI lookup patterns
    Examine JasperReports Server logs for suspicious JNDI lookup requests, particularly those containing ldap://, rmi://, or dns:// protocols pointing to external addresses
    Affected if Unusual JNDI lookup entries appear in logs, indicating potential exploitation attempts
  5. Check for unauthorized scheduled reports or data source modifications
    Review recently created or modified scheduled jobs and data source configurations for suspicious changes that may indicate post-exploitation activity
    Affected if Unexpected scheduled reports or data source configurations exist that were not created by authorized administrators

A system is affected if it runs JasperReports Server version 8.0.2 or lower, or exactly version 8.1.0, and has JNDI Data Sources configured and accessible over the network.

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 TIBCO JasperReports Server to a patched version (above 8.1.0) or apply vendor-provided patches; restrict administrative access and network exposure while awaiting remediation.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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