Ebx Add OnsPlugin / extension · Tibco

CVE-2019-17332

MEDIUM · 5.4 CVSS v3.1 Published 2019-11-12
Fix available
A fix is available. Upgrade to after 3.20.13 or later.
See remediation →
58/100
Remediation priority · Elevated
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 Digital Asset Manager Web Interface component of TIBCO Software Inc.'s TIBCO EBX Add-ons contains a vulnerability that theoretically allows authenticated users to perform stored cross-site scripting (XSS) attacks. Affected releases are TIBCO Software Inc.'s TIBCO EBX Add-ons: versions up to and including 3.20.13, versions 4.1.0, 4.2.0, 4.2.1, and 4.2.2.

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

Stored cross-site scripting (XSS) vulnerability in the Digital Asset Manager Web Interface component of TIBCO EBX Add-ons allows authenticated users to inject malicious scripts. The vulnerability affects versions up to 3.20.13 and 4.1.0 through 4.2.2. Successful exploitation could allow attackers to execute arbitrary JavaScript in the browsers of other users viewing affected content.

MitigationUpgrade to a patched version of TIBCO EBX Add-ons when available. Implement proper input validation and output encoding for all user-supplied data in the Digital Asset Manager interface.

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
Ebx Add OnsPlugin / extension
Affected:<= 3.20.13= 4.1.0= 4.2.0= 4.2.1= 4.2.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 TIBCO EBX Add-ons installation
    Locate the TIBCO EBX Add-ons installation in your environment and identify the deployed version number
    Affected if TIBCO EBX Add-ons is installed and the version falls within the affected ranges: any version <= 3.20.13, or versions 4.1.0, 4.2.0, 4.2.1, 4.2.2
  2. Confirm Digital Asset Manager Web Interface is enabled
    Check the TIBCO EBX configuration to determine if the Digital Asset Manager Web Interface component is enabled and accessible
    Affected if The Digital Asset Manager Web Interface component is enabled and accessible to users
  3. Review Digital Asset Manager content for injected scripts
    Inspect stored content within the Digital Asset Manager for any suspicious JavaScript code, script tags, or event handlers in fields that accept user-supplied data
    Affected if Unexpected or malicious JavaScript code is found stored in Digital Asset Manager content fields
  4. Check user activity logs for XSS injection attempts
    Review authentication logs and Digital Asset Manager access logs for any patterns indicating injection attempts or unusual script-related activity
    Affected if Logs show injection attempts or unusual script execution patterns associated with the Digital Asset Manager interface

You are affected if TIBCO EBX Add-ons is installed with a version matching <= 3.20.13, 4.1.0, 4.2.0, 4.2.1, or 4.2.2 AND the Digital Asset Manager Web Interface component is enabled and accessible to authenticated users.

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

Upgrade to a patched version of TIBCO EBX Add-ons when available. Implement proper input validation and output encoding for all user-supplied data in the Digital Asset Manager interface.

Fix this in Ebx Add Ons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
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,536.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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