dbcve.org
EbxApplication · Tibco

CVE-2021-35498

CRITICAL · 9.8 CVSS v3.1 Published 2021-10-13
Fix available
A fix is available. Upgrade to 5.8.124 / 5.9.15 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 TIBCO EBX Web Server component of TIBCO Software Inc.'s TIBCO EBX, TIBCO EBX, TIBCO EBX, and TIBCO Product and Service Catalog powered by TIBCO EBX contains a vulnerability that under certain specific conditions allows an attacker to enter a password other than the legitimate password and it will be accepted as valid. Affected releases are TIBCO Software Inc.'s TIBCO EBX: versions 5.8.123 and below, TIBCO EBX: versions 5.9.3, 5.9.4, 5.9.5, 5.9.6, 5.9.7, 5.9.8, 5.9.9, 5.9.10, 5.9.11, 5.9.12, 5.9.13, and 5.9.14, TIBCO EBX: versions 6.0.0 and 6.0.1, and TIBCO Product and Service Catalog powered by TIBCO EBX: version 1.0.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 · high confidence

The TIBCO EBX Web Server contains an authentication bypass vulnerability where the password validation logic accepts any password entered (other than the legitimate password) as valid. This is a critical logic flaw that completely undermines the authentication mechanism, allowing unauthorized access without knowing the actual credentials.

MitigationApply the vendor-supplied patches to upgrade to a fixed version of TIBCO EBX. Until patched, restrict network access to the EBX Web Server to reduce exposure.

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
EbxApplication
Affected:< 5.8.124>= 5.9.3, < 5.9.15>= 6.0.0, < 6.0.2
Product And Service Catalog Powered By Tibco EbxApplication
Affected:= 1.0.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
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 the TIBCO EBX version
    Locate the EBX version information in the installation directory, typically in a version.properties file or accessible via the EBX administration interface under the 'About' or 'Version' section
    Affected if The installed version is less than 5.8.124, or greater than or equal to 5.9.3 but less than 5.9.15, or greater than or equal to 6.0.0 but less than 6.0.2
  2. Check for Tibco Product And Service Catalog variant
    If your deployment includes Tibco Product And Service Catalog powered by Tibco EBX, verify the exact version number of this specific product
    Affected if The version is exactly 1.0.0
  3. Confirm EBX Web Server is exposed
    Verify that the EBX web interface is accessible by accessing the login URL (commonly at /ebx/ on the configured HTTP/HTTPS port) from the network
    Affected if The EBX Web Server is reachable and accepts authentication attempts

The environment is affected if the installed EBX version falls within the vulnerable ranges (<5.8.124, >=5.9.3 to <5.9.15, or >=6.0.0 to <6.0.2) and the EBX Web Server is network-accessible.

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 5.8.124 / 5.9.15 / 6.0.2 or later
Fixed in 5.8.1245.9.156.0.2
Interim mitigation

Apply the vendor-supplied patches to upgrade to a fixed version of TIBCO EBX. Until patched, restrict network access to the EBX Web Server to reduce exposure.

Recommended fix High confidence

Upgrade to EBX 5.8.124, 5.9.15, or 6.0.2 (or later) depending on your current version branch

  1. 1. Identify the current TIBCO EBX version by checking the installed product or administration console
  2. 2. Determine which upgrade path applies based on your current version branch (5.8.x, 5.9.x, or 6.0.x)
  3. 3. Back up the current EBX installation, including all configuration files and data repositories
  4. 4. For 5.8.x versions: upgrade to version 5.8.124 or later
  5. 5. For 5.9.x versions (5.9.3 through 5.9.14): upgrade to version 5.9.15 or later
  6. 6. For 6.0.x versions (6.0.0 or 6.0.1): upgrade to version 6.0.2 or later
  7. 7. For Product and Service Catalog powered by TIBCO EBX 1.0.0: upgrade to the latest available version that includes the EBX security fix
  8. 8. After upgrade, verify the authentication mechanism properly rejects invalid passwords
Caveat Review TIBCO release notes for migration considerations between version branches; test thoroughly in a non-production environment before deploying

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

Fix this in Ebx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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