dbcve.org
BusinessconnectApplication · Tibco

CVE-2021-43050

HIGH · 7.8 CVSS v3.1 Published 2022-02-15
Fix available
A fix is available. Upgrade to 1.1.1 or later.
See remediation →
80/100
Remediation priority · High
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 Auth Server component of TIBCO Software Inc.'s TIBCO BusinessConnect Container Edition contains an easily exploitable vulnerability that allows an unauthenticated attacker with local access to obtain administrative usernames and passwords for the affected system. Affected releases are TIBCO Software Inc.'s TIBCO BusinessConnect Container Edition: versions 1.1.0 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 · moderate confidence

The Auth Server component in TIBCO BusinessConnect Container Edition versions 1.1.0 and below contains a vulnerability allowing an unauthenticated attacker with local system access to obtain administrative usernames and passwords for the affected system. This is a local credential disclosure vulnerability with high impact due to the privilege level obtained.

MitigationUpgrade TIBCO BusinessConnect Container Edition to a version above 1.1.0 or apply the vendor-supplied patch. Restrict local access to the server to mitigate the attack vector.

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
BusinessconnectApplication
Affected:< 1.1.1

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

CVSS:3.1/AV:L/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 if TIBCO BusinessConnect Container Edition is installed
    Look for BusinessConnect installation directories, check for tibco businessconnect processes running (ps aux | grep -i businessconnect), or review software inventory records
    Affected if BusinessConnect Container Edition is present on the system
  2. Determine the installed version of BusinessConnect Container Edition
    Check the version information in the installation directory, typically found in a version manifest, about file, or check the Docker/container image tag if using containerized deployment
    Affected if The installed version is 1.1.0 or below, or the version cannot be determined and BusinessConnect is present
  3. Verify the Auth Server component is in use
    Confirm that the Auth Server component of BusinessConnect Container Edition is deployed and running as part of the installation
    Affected if Auth Server component is configured and running
  4. Confirm local access to the server exists
    Review system access controls and audit logs to determine if any untrusted local users or processes have access to the server where BusinessConnect is installed
    Affected if Untrusted local users or processes have access to the server where BusinessConnect Container Edition is hosted

The environment is affected if TIBCO BusinessConnect Container Edition version 1.1.0 or below is installed and the Auth Server component is running, since an attacker with local system access could exploit the credential disclosure vulnerability.

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 1.1.1 or later
Fixed in 1.1.1
Interim mitigation

Upgrade TIBCO BusinessConnect Container Edition to a version above 1.1.0 or apply the vendor-supplied patch. Restrict local access to the server to mitigate the attack vector.

Recommended fix Moderate confidence

TIBCO BusinessConnect Container Edition 1.1.1

  1. 1. Back up the current TIBCO BusinessConnect Container Edition installation and all configuration files.
  2. 2. Download TIBCO BusinessConnect Container Edition version 1.1.1 or later from the official TIBCO support portal.
  3. 3. Stop the currently running BusinessConnect Container Edition instance.
  4. 4. Install version 1.1.1 following the standard TIBCO installation documentation.
  5. 5. Restore any custom configurations from the backup, ensuring compatibility with version 1.1.1.
  6. 6. Start the BusinessConnect Container Edition service and verify it is running correctly.
  7. 7. Test the Auth Server component to confirm the vulnerability is remediated and administrative credentials are no longer exposed.
Caveat Review TIBCO release notes for 1.1.1 to check for any configuration or behavioral changes that may affect existing deployments

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

Fix this in Businessconnect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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