dbcve.org
EftlApplication · Tibco

CVE-2021-43054

HIGH · 8.8 CVSS v3.1 Published 2022-01-11
Fix available
A fix is available. Upgrade to after 6.7.2 or later.
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 eFTL Server component of TIBCO Software Inc.'s TIBCO eFTL - Community Edition, TIBCO eFTL - Developer Edition, and TIBCO eFTL - Enterprise Edition contains an easily exploitable vulnerability that allows a low privileged attacker with network access to generate API tokens that can access any other channel with arbitrary permissions. Affected releases are TIBCO Software Inc.'s TIBCO eFTL - Community Edition: versions 6.7.2 and below, TIBCO eFTL - Developer Edition: versions 6.7.2 and below, and TIBCO eFTL - Enterprise Edition: versions 6.7.2 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

The eFTL Server component contains an authorization bypass vulnerability where a low-privileged attacker with network access can generate API tokens that grant access to any channel with arbitrary permissions, effectively bypassing proper permission boundaries.

MitigationUpgrade TIBCO eFTL to a version higher than 6.7.2. As an interim measure, restrict network access to the eFTL Server and implement additional access controls.

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
EftlApplication
Affected:<= 6.7.2

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 installed eFTL version
    Locate the eFTL installation directory and check the version file or executable properties. Common locations include the TIBCO home directory under eftl/. Run 'eftl version' or check version.info if available.
    Affected if The installed version is 6.7.2 or lower
  2. Verify eFTL Server is running
    Check if the eFTL Server process is active on the system. Use commands like 'ps aux | grep eftl' on Linux or check Windows services for eFTL-related services.
    Affected if The eFTL Server process is running and responding to requests
  3. Check eFTL Server network exposure
    Determine if the eFTL Server is bound to a network interface and accessible. Check configuration files (typically eftl.conf or similar) for bind address settings, and use netstat or ss to identify listening ports (default eFTL ports are 8080, 8443).
    Affected if The eFTL Server is listening on a non-localhost IP address and is reachable from the network
  4. Confirm token generation endpoint is accessible
    Test access to the eFTL API token generation endpoint (typically /eftl/token or similar) by sending an HTTP request without proper authentication or with a low-privilege account.
    Affected if API tokens can be generated without proper authorization checks

You are affected if eFTL version 6.7.2 or lower is installed and the eFTL Server is running and network-accessible, allowing unauthorized token generation.

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

Upgrade TIBCO eFTL to a version higher than 6.7.2. As an interim measure, restrict network access to the eFTL Server and implement additional access controls.

Recommended fix Moderate confidence

eFTL version 6.7.3 or later (contact TIBCO to confirm the exact fixed release)

  1. Contact TIBCO customer support to obtain the patched release of eFTL that addresses CVE-2021-43054
  2. Plan an upgrade to eFTL version 6.7.3 or later (verify with TIBCO that this version contains the fix)
  3. Before upgrading, backup all eFTL configuration files and data
  4. Schedule a maintenance window for the upgrade
  5. Stop the eFTL server gracefully
  6. Upgrade eFTL to the fixed version using TIBCO's standard upgrade procedure
  7. Verify the upgrade was successful by checking the eFTL server status
  8. Review API token generation to confirm the vulnerability is remediated
Caveat Check TIBCO release notes for version 6.7.3+ for any breaking changes or migration requirements

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

Fix this in Eftl 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 the upgrade done

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-2021-43054 — 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-43054 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