dbcve.org
Api Exchange GatewayApplication · Tibco

CVE-2021-23274

CRITICAL · 9.8 CVSS v3.1 Published 2021-03-23
Fix available
A fix is available. Upgrade to after 2.3.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Config UI component of TIBCO Software Inc.'s TIBCO API Exchange Gateway and TIBCO API Exchange Gateway Distribution for TIBCO Silver Fabric contains a vulnerability that theoretically allows an unauthenticated attacker with network access to execute a clickjacking attack on the affected system. A successful attack using this vulnerability does not require human interaction from a person other than the attacker. Affected releases are TIBCO Software Inc.'s TIBCO API Exchange Gateway: versions 2.3.3 and below and TIBCO API Exchange Gateway Distribution for TIBCO Silver Fabric: versions 2.3.3 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

Clickjacking vulnerability in the Config UI component of TIBCO API Exchange Gateway allows unauthenticated remote attackers to embed the UI in an invisible iframe and trick users into performing unintended actions. The high CVSS score reflects the trivial network-based exploitation and lack of authentication requirement.

MitigationImplement X-Frame-Options: DENY or SAMEORIGIN header, or Content-Security-Policy with frame-ancestors directive, at the web server or load balancer level to prevent the Config UI from being embedded in iframes.

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
Api Exchange GatewayApplication
Affected:<= 2.3.3
Api Exchange Gateway DistributionApplication
Affected:<= 2.3.3

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

CVSS:3.1/AV:N/AC:L/PR:N/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 TIBCO API Exchange Gateway version
    Locate the installation directory and check version.txt, manifest, or bw version information. Common paths include $TIBCO_HOME/api-exchange-gateway/ or check the bw version command if deployed on BusinessWorks.
    Affected if The installed version is 2.3.3 or lower.
  2. Verify Config UI component is deployed
    Check if the Config UI web application is deployed and accessible. Look for the /api-gateway-config or similar UI endpoint in the deployed web applications or check the web.xml deployment descriptor.
    Affected if The Config UI component is deployed and accessible via HTTP/HTTPS.
  3. Test for missing X-Frame-Options header
    Send an HTTP request to the Config UI endpoint (such as the login or main config page) and inspect the response headers for the presence of X-Frame-Options. Use curl -I <config-ui-url> and examine headers.
    Affected if The X-Frame-Options header is absent from the Config UI responses.
  4. Test for missing CSP frame-ancestors directive
    Send an HTTP request to the Config UI endpoint and inspect the Content-Security-Policy header for the frame-ancestors directive. Use curl -I <config-ui-url> and check for CSP header.
    Affected if The Content-Security-Policy header is absent or does not include frame-ancestors directive to block iframe embedding.
  5. Confirm iframe embeddability
    Attempt to embed the Config UI URL in an iframe within a test HTML page and verify it loads successfully without being blocked by the browser.
    Affected if The Config UI can be successfully embedded in a third-party iframe without browser restrictions.

A user is affected if running TIBCO API Exchange Gateway version 2.3.3 or lower, the Config UI is exposed, and neither X-Frame-Options nor CSP frame-ancestors headers are present to prevent clickjacking.

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 2.3.3
Interim mitigation

Implement X-Frame-Options: DENY or SAMEORIGIN header, or Content-Security-Policy with frame-ancestors directive, at the web server or load balancer level to prevent the Config UI from being embedded in iframes.

Fix this in Api Exchange Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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