dbcve.org
FtlApplication · Tibco

CVE-2021-43052

HIGH · 7.5 CVSS v3.1 Published 2022-01-11
Fix available
A fix is available. Upgrade to after 6.7.2 or later.
See remediation →
84/100
Remediation priority · High
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 Realm Server component of TIBCO Software Inc.'s TIBCO FTL - Community Edition, TIBCO FTL - Developer Edition, and TIBCO FTL - Enterprise Edition contains an easily exploitable vulnerability that allows authentication bypass due to a hard coded secret used in the default realm server of the affected system. Affected releases are TIBCO Software Inc.'s TIBCO FTL - Community Edition: versions 6.7.2 and below, TIBCO FTL - Developer Edition: versions 6.7.2 and below, and TIBCO FTL - 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 TIBCO FTL Realm Server contains a hardcoded secret in its default configuration that allows attackers to bypass authentication. This affects the Community, Developer, and Enterprise editions of FTL versions 6.7.2 and below.

MitigationReplace the hardcoded secret with a unique, strong credential and update to a patched version if available. Verify all authentication paths use the new credentials.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed FTL version
    Run the FTL version command or check the installed package metadata. On Linux, this may be in /opt/tibco/ftl/ or the equivalent installation directory. Look for a version file or use the tibftl-server -v command if available.
    Affected if The installed version is 6.7.2 or lower.
  2. Locate the Realm Server configuration file
    Find the FTL realm server configuration, typically stored in the realm server configuration directory or configuration folder. This is commonly in the conf or config subdirectory of the FTL installation.
    Affected if The configuration file exists and was not modified from defaults.
  3. Check for hardcoded secret in realm configuration
    Open the realm server configuration file and search for authentication-related settings. Look for embedded credentials, keys, or secrets used for authentication that appear to be default or static values rather than custom-generated ones.
    Affected if A hardcoded secret or default credential is present in the configuration file.
  4. Verify if default authentication is still in use
    Compare the active authentication configuration against what would be the product defaults. Check whether the secret/credential has been changed from any documented default values or remains at factory-set values.
    Affected if The authentication secret matches default values and has not been replaced with a unique credential.

You are affected if you are running FTL version 6.7.2 or lower AND the Realm Server is using the default hardcoded secret in its configuration instead of a custom, unique credential.

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

Replace the hardcoded secret with a unique, strong credential and update to a patched version if available. Verify all authentication paths use the new credentials.

Recommended fix Moderate confidence

Contact TIBCO support for the specific fixed version (seek version > 6.7.2)

  1. Check TIBCO FTL product updates or contact TIBCO support for the latest patched version that addresses CVE-2021-43052
  2. Obtain the updated installer for the fixed release from TIBCO's official download portal or support channels
  3. Back up the current TIBCO FTL configuration, realm definitions, and any custom settings
  4. Deploy the updated TIBCO FTL version in a test environment to verify application compatibility
  5. Validate that the hard-coded credential has been removed or changed in the Realm Server component
  6. Deploy the updated version to production after successful testing
Caveat Review TIBCO release notes for the fixed version to check for any compatibility or configuration changes that may affect your deployment

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

Fix this in Ftl Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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