AdministratorApplication · Tibco

CVE-2021-28829

HIGH · 8.0 CVSS v3.1 Published 2021-04-20
Fix available
A fix is available. Upgrade to after 5.10.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 Administration GUI component of TIBCO Software Inc.'s TIBCO Administrator - Enterprise Edition, TIBCO Administrator - Enterprise Edition, TIBCO Administrator - Enterprise Edition Distribution for TIBCO Silver Fabric, TIBCO Administrator - Enterprise Edition Distribution for TIBCO Silver Fabric, TIBCO Administrator - Enterprise Edition for z/Linux, and TIBCO Administrator - Enterprise Edition for z/Linux contains an easily exploitable vulnerability that allows a low privileged attacker with network access to execute a persistent CSV injection attack from the affected system. A successful attack using this vulnerability requires human interaction from a person other than the attacker. Affected releases are TIBCO Software Inc.'s TIBCO Administrator - Enterprise Edition: versions 5.10.2 and below, TIBCO Administrator - Enterprise Edition: versions 5.11.0 and 5.11.1, TIBCO Administrator - Enterprise Edition Distribution for TIBCO Silver Fabric: versions 5.10.2 and below, TIBCO Administrator - Enterprise Edition Distribution for TIBCO Silver Fabric: versions 5.11.0 and 5.11.1, TIBCO Administrator - Enterprise Edition for z/Linux: versions 5.10.2 and below, and TIBCO Administrator - Enterprise Edition for z/Linux: versions 5.11.0 and 5.11.1.

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

A persistent CSV injection vulnerability exists in the Administration GUI component of TIBCO Administrator - Enterprise Edition. A low-privileged attacker can inject malicious formulas (starting with =, +, -, @, tab, or carriage return characters) into data fields. When a legitimate user exports data to CSV and opens it in a spreadsheet application, the formulas execute, potentially allowing arbitrary command execution or data exfiltration.

MitigationApply vendor patches for affected versions (5.10.2 and below, 5.11.0, 5.11.1). Until patched, disable or restrict CSV export functionality in the Administration GUI and implement input validation to escape formula-special characters in all exported data fields.

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
AdministratorApplication
Affected:<= 5.10.2= 5.11.0= 5.11.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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Determine the installed TIBCO Administrator version
    Locate the TIBCO Administrator installation directory and check the version information file, or run the product version command if available. Common locations include the installation root or a 'version.txt' file within the product directory.
    Affected if The installed version is 5.10.2 or lower, exactly 5.11.0, or exactly 5.11.1.
  2. Identify if the Administration GUI CSV export feature is present and accessible
    Log in to the TIBCO Administration GUI as a low-privileged user and navigate through the interface to locate any data export or CSV download options. Check for export functionality in data grids, reports, or user management sections.
    Affected if CSV export functionality is available and accessible to the user account being tested.
  3. Verify low-privileged user write access to data fields
    Using a low-privileged account, attempt to create or modify records in the Administration GUI. Focus on fields such as user details, configuration parameters, or any data that can be exported.
    Affected if Low-privileged users can create or modify data fields that are included in CSV exports.
  4. Inspect stored data for formula injection characters
    Query the underlying database or view stored data through the GUI to examine if any existing fields contain characters that initiate CSV formula injection: =, +, -, @, tab (0x09), or carriage return (0x0D) as the first character of a field value.
    Affected if Any data fields contain values starting with =, +, -, @, tab, or CR characters.
  5. Review recent CSV export files
    Locate any recently exported CSV files from the Administration GUI. Open them in a spreadsheet application or inspect the raw file content to check for unescaped formula characters in the exported data.
    Affected if Exported CSV files contain formula characters (=, +, -, @) that are not escaped with a leading single quote or other mitigation.

You are affected if TIBCO Administrator version is 5.10.2 or lower, 5.11.0, or 5.11.1 AND the Administration GUI CSV export feature is accessible to low-privileged users who can inject formula characters into data fields.

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

Apply vendor patches for affected versions (5.10.2 and below, 5.11.0, 5.11.1). Until patched, disable or restrict CSV export functionality in the Administration GUI and implement input validation to escape formula-special characters in all exported data fields.

Fix this in Administrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-28829 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-28829 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