dbcve.org
Spotfire ServerApplication · Tibco

CVE-2021-43051

MEDIUM · 6.8 CVSS v3.1 Published 2021-12-14
Fix available
A fix is available. Upgrade to after 10.10.6 or later.
See remediation →
72/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 Spotfire Server component of TIBCO Software Inc.'s TIBCO Spotfire Server, TIBCO Spotfire Server, and TIBCO Spotfire Server contains a difficult to exploit vulnerability that allows malicious custom API clients with network access to execute internal API operations outside of the scope of those granted to it. A successful attack using this vulnerability requires human interaction from a person other than the attacker. Affected releases are TIBCO Software Inc.'s TIBCO Spotfire Server: versions 10.10.6 and below, TIBCO Spotfire Server: versions 11.0.0, 11.1.0, 11.2.0, 11.3.0, 11.4.0, and 11.4.1, and TIBCO Spotfire Server: versions 11.5.0 and 11.6.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 Spotfire Server contains an authorization bypass vulnerability where malicious custom API clients with network access can execute internal API operations outside their granted scope. The flaw appears to be in the server's API access control enforcement, allowing clients to access internal operations they should not be permitted to reach.

MitigationUpgrade TIBCO Spotfire Server to a patched version beyond 11.6.0. If immediate patching is not feasible, restrict network access to the Spotfire Server API and monitor for unauthorized internal API calls.

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
Spotfire ServerApplication
Affected:<= 10.10.6= 11.0.0= 11.1.0= 11.2.0= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.6.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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 the installed Spotfire Server version
    Locate the Spotfire Server installation directory and check the version file, or access the server admin web interface and navigate to the About or Server Information section
    Affected if The installed version matches <= 10.10.6, = 11.0.0, = 11.1.0, = 11.2.0, = 11.3.0, = 11.4.0, = 11.4.1, = 11.5.0, or = 11.6.0
  2. Verify if custom API clients are configured
    Access the Spotfire Server administration interface and review the API Clients configuration panel to identify any custom API client registrations
    Affected if One or more custom API clients exist with granted scopes that could be exploited to access internal operations
  3. Inspect API access control configuration
    Review the Spotfire Server security configuration files (typically in the server configuration directory) or the admin interface API authorization settings to verify which operations are permitted for non-administrative API clients
    Affected if API access control rules allow custom clients to reach internal endpoint operations beyond their intended scope
  4. Check network exposure of the Spotfire Server API
    Determine if the Spotfire Server API endpoints (typically ports 8080, 8443, or configured HTTP/HTTPS ports) are accessible from untrusted networks or the public internet
    Affected if The API is exposed to networks where untrusted or malicious clients could connect
  5. Review API access logs for unauthorized internal calls
    Examine Spotfire Server access logs and API audit logs for patterns where custom API clients are calling internal administrative or privileged operations outside their documented scope
    Affected if Logs show API clients making calls to internal operations that should be restricted based on their assigned permissions

You are affected if your Spotfire Server version is one of the listed vulnerable versions AND you have custom API clients with network access that could potentially bypass authorization controls to access internal operations.

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 a release after 10.10.6
Interim mitigation

Upgrade TIBCO Spotfire Server to a patched version beyond 11.6.0. If immediate patching is not feasible, restrict network access to the Spotfire Server API and monitor for unauthorized internal API calls.

Recommended fix High confidence

Upgrade to Spotfire Server 10.10.7, 11.3.2, 11.4.2, 11.5.2, or 11.6.2 (or latest 11.x LTS) depending on your current major version branch

  1. 1. Identify the current Spotfire Server version by checking the server administration console or using the Spotfire Server configuration tool.
  2. 2. Based on the current version, determine the appropriate upgrade path: if using 10.10.x, upgrade to 10.10.7; if using 11.0.0-11.2.x, upgrade to 11.3.2 or later; if using 11.3.x, upgrade to 11.3.2; if using 11.4.x, upgrade to 11.4.2 or later; if using 11.5.x or 11.6.x, upgrade to 11.6.2 or the latest 11.x LTS release.
  3. 3. Review TIBCO Spotfire Server upgrade documentation for your specific version transition, including backup procedures.
  4. 4. Perform a full backup of the Spotfire database, configuration files, and deployment directory.
  5. 5. Download the appropriate Spotfire Server installer from TIBCO's official support site (https://support.tibco.com/).
  6. 6. Run the installer on the Spotfire Server, following the upgrade wizard instructions.
  7. 7. After upgrade, verify that Spotfire Server services start correctly.
  8. 8. Confirm the vulnerability is resolved by checking that custom API clients can no longer access internal API operations outside their granted scope.
Caveat Review TIBCO upgrade notes for your version path; some configuration changes or re-import of certain settings may be required between major version branches

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

Fix this in Spotfire Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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