dbcve.org
Ebx Add OnsPlugin / extension · Tibco

CVE-2020-27148

HIGH · 7.1 CVSS v3.1 Published 2021-01-12
Fix available
A fix is available. Upgrade to after 4.4.2 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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 Add-on for Oracle Hyperion EPM, TIBCO EBX Data Exchange Add-on, and TIBCO EBX Insight Add-on components of TIBCO Software Inc.'s TIBCO EBX Add-ons contain a vulnerability that theoretically allows a low privileged attacker with network access to execute an XML External Entity (XXE) attack. Affected releases are TIBCO Software Inc.'s TIBCO EBX Add-ons: versions 4.4.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

TIBCO EBX Add-on components (EBX Add-on for Oracle Hyperion EPM, EBX Data Exchange Add-on, and EBX Insight Add-on) versions 4.4.2 and below contain an XML External Entity (XXE) vulnerability. A low-privileged attacker with network access can exploit this by crafting malicious XML input that references external entities, potentially reading sensitive files or causing denial of service.

MitigationUpgrade TIBCO EBX Add-ons to a version above 4.4.2, or apply vendor-provided patches. If immediate patching is not possible, disable XML external entity processing in the application configuration and validate/sanitize XML input.

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:<= 4.4.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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

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 TIBCO EBX Add-on version
    Locate the TIBCO EBX Add-on installation directory and check the version manifest, about file, or version.properties. Common locations include the lib or conf folders within the EBX add-on installation. Use the product's built-in version check if available in the administration console.
    Affected if The installed version is 4.4.2 or lower.
  2. Confirm EBX Add-on component type
    Identify which EBX add-on component is in use: EBX Add-on for Oracle Hyperion EPM, EBX Data Exchange Add-on, or EBX Insight Add-on. Check the installed component list or product naming in the installation directory.
    Affected if Any of these three add-on components are present in version 4.4.2 or below.
  3. Check for XML input processing
    Determine if the application accepts XML input through any API endpoint, file upload, data import feature, or web service. Review application logs and configuration for XML parsing activity.
    Affected if The application processes XML input from users or external sources.
  4. Inspect XML parser configuration
    Examine the XML parser configuration files or settings used by the EBX add-on. Look for settings related to external entity processing, DOCTYPE declarations, or XXE handling in the application configuration.
    Affected if XML parser is configured to allow external entities or does not have XXE protection explicitly disabled.
  5. Review network exposure
    Verify network accessibility of the EBX add-on web interfaces or APIs. Check firewall rules and access controls for endpoints that accept XML submissions.
    Affected if The XML processing interface is accessible over the network to low-privileged users.

You are affected if you have any TIBCO EBX Add-on (EBX Add-on for Oracle Hyperion EPM, EBX Data Exchange Add-on, or EBX Insight Add-on) installed at version 4.4.2 or below and that component accepts XML input over the network.

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

Upgrade TIBCO EBX Add-ons to a version above 4.4.2, or apply vendor-provided patches. If immediate patching is not possible, disable XML external entity processing in the application configuration and validate/sanitize XML input.

Fix this in Ebx Add Ons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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