dbcve.org
RendezvousApplication · Tibco

CVE-2021-28818

HIGH · 7.8 CVSS v3.1 Published 2021-03-23
Fix available
A fix is available. Upgrade to after 8.5.1 or later.
See remediation →
80/100
Remediation priority · High
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 Rendezvous Routing Daemon (rvrd), Rendezvous Secure Routing Daemon (rvrsd), Rendezvous Secure Daemon (rvsd), Rendezvous Cache (rvcache), Rendezvous Secure C API, Rendezvous Java API, and Rendezvous .Net API components of TIBCO Software Inc.'s TIBCO Rendezvous and TIBCO Rendezvous Developer Edition contain a vulnerability that theoretically allows a low privileged attacker with local access on the Windows operating system to insert malicious software. The affected component can be abused to execute the malicious software inserted by the attacker with the elevated privileges of the component. This vulnerability results from the affected component searching for run-time artifacts outside of the installation hierarchy. Affected releases are TIBCO Software Inc.'s TIBCO Rendezvous: versions 8.5.1 and below and TIBCO Rendezvous Developer Edition: versions 8.5.1 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

This is a local privilege escalation vulnerability in TIBCO Rendezvous components on Windows. The affected components (rvrd, rvrsd, rvsd, rvcache, and API libraries) search for run-time artifacts outside their installation directory, allowing a low-privileged attacker to place malicious files that get executed with the elevated privileges of the TIBCO service.

MitigationUpgrade TIBCO Rendezvous to a version above 8.5.1. Until patched, restrict file system access to prevent unauthorized placement of malicious files in locations searched by the components.

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
RendezvousApplication
Affected:<= 8.5.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 if TIBCO Rendezvous is installed on Windows
    Check for TIBCO Rendezvous installation directories, typically under C:\Program Files\TIBCO\ or C:\TIBCO\, and look for Rendezvous components in the file system or installed programs list.
    Affected if TIBCO Rendezvous is found installed on the system
  2. Determine the installed version of TIBCO Rendezvous
    Locate the version information in the installation directory, typically in a version file, readme, or executable metadata. Compare the version number to the affected range.
    Affected if The installed version is 8.5.1 or lower
  3. Verify presence of affected components
    Check the installation for the vulnerable components: rvrd.exe, rvrsd.exe, rvsd.exe, rvcache.exe, or associated API libraries (TIB/rv.dll or similar).
    Affected if Any of the affected components (rvrd, rvrsd, rvsd, rvcache, or API libraries) are present
  4. Confirm TIBCO Rendezvous services run with elevated privileges
    Open Windows Services (services.msc), locate TIBCO Rendezvous services (rvrd, rvrsd, rvsd, or rvcache), right-click and view Properties to check the 'Log on as' account. Services running as LocalSystem or a privileged account indicate elevated privileges.
    Affected if Any TIBCO Rendezvous service runs under a privileged account (such as LocalSystem or a domain administrator)
  5. Check file system permissions on searched directories
    Identify directories outside the TIBCO installation that may be searched by the Rendezvous components (commonly the Windows system PATH locations, user temp directories, or working directories). Use icacls or File Explorer security tab to verify if low-privileged users have write access to these locations.
    Affected if Low-privileged users can write to directories that TIBCO Rendezvous components search for run-time artifacts

A user is affected if TIBCO Rendezvous version 8.5.1 or lower is installed on Windows with any of the affected components running as a privileged service, and low-privileged users can write to directories searched by those components.

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.5.1
Interim mitigation

Upgrade TIBCO Rendezvous to a version above 8.5.1. Until patched, restrict file system access to prevent unauthorized placement of malicious files in locations searched by the components.

Fix this in Rendezvous Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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