dbcve.org
Messaging ApplianceApplication · Tibco

CVE-2015-4555

HIGH · 7.5 CVSS v2.0 Published 2015-08-30
Fix available
A fix is available. Upgrade to after 8.7.1 or later.
See remediation →
84/100
Remediation priority · High
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
Buffer overflow in the HTTP administrative interface in TIBCO Rendezvous before 8.4.4, Rendezvous Network Server before 1.1.1, Substation ES before 2.9.0, and Messaging Appliance before 8.7.2 allows remote attackers to cause a denial of service or possibly execute arbitrary code via unspecified vectors, related to the Rendezvous Daemon (rvd), Routing Daemon (rvrd), Secure Daemon (rvsd), Secure Routing Daemon (rvsrd), Gateway Daemon (rvgd), Daemon Adapter (rvda), Cache (rvcache), Agent (rva), and Relay Agent (rvrad) components.

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

Buffer overflow in the HTTP administrative interface of TIBCO Rendezvous components (rvd, rvrd, rvsd, rvsrd, rvgd, rvda, rvcache, rva, rvrad) allows remote attackers to cause denial of service or potentially execute arbitrary code via unspecified vectors.

MitigationUpgrade to TIBCO Rendezvous 8.4.4+, Rendezvous Network Server 1.1.1+, Substation ES 2.9.0+, or Messaging Appliance 8.7.2+ to patch the vulnerability.

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
Messaging ApplianceApplication
Affected:<= 8.7.1
RendezvousApplication
Affected:<= 8.4.3
Rendezvous Network ServerApplication
Affected:<= 1.1.0
Substation EsApplication
Affected:<= 2.8.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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 product and version
    Run 'rvd --version' or 'rvrd --version' to check the Rendezvous daemon version. For Messaging Appliance check 'tibcohawkserver --version' or check the installation directory for version files. For Substation ES check the installation path for version information.
    Affected if The installed version is at or below 8.4.3 for Rendezvous, 1.1.0 for Rendezvous Network Server, 8.7.1 for Messaging Appliance, or 2.8.1 for Substation ES.
  2. Verify HTTP administrative interface is enabled
    Check the TIBCO configuration files (typically in the product's conf directory) for HTTP admin settings. Look for parameters like 'http-port', 'admin-port', or similar HTTP interface configurations. Also check if the service is configured to start with HTTP admin enabled.
    Affected if HTTP administrative interface is explicitly enabled in the configuration files.
  3. Check for listening HTTP admin ports
    Run 'netstat -an | grep -E "(7580|7581|7582)"' or 'ss -tlnp | grep -E "(7580|7581|7582)"' to see if the typical TIBCO HTTP admin ports are listening. Adjust port numbers based on your specific configuration.
    Affected if Ports used by the HTTP administrative interface (commonly 7580, 7581, or configured admin ports) are in LISTEN state and accessible.
  4. Confirm vulnerable component is running
    Use 'ps aux | grep -E "(rvd|rvrd|rvsd|rvsrd|rvgd|rvda|rvcache|rva|rvrad)"' to identify which TIBCO Rendezvous components are running. Check the process list for the specific daemon processes that expose the HTTP admin interface.
    Affected if Any of the affected components (rvd, rvrd, rvsd, rvsrd, rvgd, rvda, rvcache, rva, rvrad) are running with HTTP administrative interface exposed.

You are affected if you are running any of the listed TIBCO products at or below the affected version numbers AND the HTTP administrative interface is enabled and 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.

From vendor data
Upgrade available Upgrade to a release after 8.7.1
Interim mitigation

Upgrade to TIBCO Rendezvous 8.4.4+, Rendezvous Network Server 1.1.1+, Substation ES 2.9.0+, or Messaging Appliance 8.7.2+ to patch the vulnerability.

Fix this in Messaging Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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