CVE-2021-35494
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 · uneditedThe Rest API component of TIBCO Software Inc.'s TIBCO JasperReports Server, TIBCO JasperReports Server, 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 ActiveMatrix BPM, and TIBCO JasperReports Server for Microsoft Azure contain a race condition that allows a low privileged authenticated attacker via the REST API to obtain read access to temporary objects created by other users on the affected system. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Server: versions 7.2.1 and below, TIBCO JasperReports Server: versions 7.5.0 and 7.5.1, TIBCO JasperReports Server: version 7.8.0, TIBCO JasperReports Server: version 7.9.0, TIBCO JasperReports Server - Community Edition: versions 7.8.0 and below, TIBCO JasperReports Server - Developer Edition: versions 7.9.0 and below, TIBCO JasperReports Server for AWS Marketplace: versions 7.9.0 and below, TIBCO JasperReports Server for ActiveMatrix BPM: versions 7.9.0 and below, and TIBCO JasperReports Server for Microsoft Azure: version 7.8.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 confidenceA race condition in the REST API component of TIBCO JasperReports Server allows low-privileged authenticated users to read temporary objects created by other users. The vulnerability stems from improper handling of concurrent access to temporary files/objects in the REST API, where timing differences can be exploited to bypass access controls and view objects belonging to other sessions.
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<= 7.2.1<= 7.8.0<= 7.9.0= 7.5.0= 7.5.1= 7.8.0= 7.9.0CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify JasperReports Server installation and versionCheck the installed version by reviewing the release documentation, admin console, or version file within the JasperReports Server installation directory (commonly in the /js or /apache-tomcat/webapps/jasperreports-server directory).Affected if The installed version is 7.5.0, 7.5.1, 7.8.0, 7.9.0, or any version <= 7.2.1 or <= 7.8.0 or <= 7.9.0 outside these specific releases.
-
Confirm REST API component is enabledVerify that the REST API service is accessible and operational. This is typically available at /rest_v2/ or /jasperserver-pro/rest/ endpoints under the JasperReports Server web application.Affected if The REST API endpoints are reachable and respond to requests.
-
Verify authenticated user access existsConfirm that low-privileged user accounts have been created and can authenticate to the JasperReports Server. Check the user management configuration or review authentication logs for user login activity.Affected if Low-privileged authenticated users can access the system through the REST API.
-
Check for concurrent session activityReview server logs or session management configuration to determine whether multiple users can access the REST API simultaneously, creating conditions for the race condition to be exploited.Affected if Multiple authenticated users can make concurrent REST API requests.
-
Compare installed version against affected rangesIf the exact version cannot be determined, compare your installation against all affected version patterns: <= 7.2.1, 7.5.0, 7.5.1, <= 7.8.0, 7.8.0, <= 7.9.0, 7.9.0.Affected if Your version matches any of the affected versions or falls within the affected ranges.
You are affected if JasperReports Server is running with a version matching 7.5.0, 7.5.1, 7.8.0, 7.9.0, or any version <= 7.2.1, <= 7.8.0, or <= 7.9.0, and the REST API is accessible to low-privileged authenticated users who can have concurrent sessions.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches for the specific affected versions. If patches are unavailable, consider restricting REST API access to trusted users or implementing additional session isolation controls at the infrastructure level.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35494 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-35494 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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