CVE-2021-28817
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 · uneditedThe Windows Installation component of TIBCO Software Inc.'s TIBCO Rendezvous and TIBCO Rendezvous Developer Edition contains a vulnerability that theoretically allows a low privileged attacker with local access on some versions of 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 a lack of access restrictions on certain files and/or folders in the installation. 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 confidenceThis is a local privilege escalation vulnerability in the Windows installer for TIBCO Rendezvous. The installer creates files/folders with overly permissive access controls, allowing a low-privileged local attacker to replace or modify executables in the installation directory. When the installer or its components run, they execute the attacker's malicious code with elevated (SYSTEM or administrator) privileges.
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<= 8.5.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify TIBCO Rendezvous installation pathCheck the Windows registry under HKLM\SOFTWARE\TIBCO\Rendezvous for the InstallPath value, or look in common locations like C:\Program Files\TIBCO\Rendezvous or C:\Program Files (x86)\TIBCO\RendezvousAffected if TIBCO Rendezvous is installed and the installation path is found on the system
-
Determine installed Tibco Rendezvous versionCheck the version of the rv.exe or tibrvjms.dll file in the installation directory by right-clicking the file, selecting Properties, and viewing the Details tab, or use PowerShell: Get-Item 'C:\Program Files\TIBCO\Rendezvous\rv.exe' | Select-Object VersionInfoAffected if The installed version is 8.5.1 or any version lower than 8.5.1
-
Verify permissions on installation directoryRight-click the TIBCO Rendezvous installation folder, select Properties, go to the Security tab, and examine the permissions for Users or authenticated users group. Alternatively, run: icacls 'C:\Program Files\TIBCO\Rendezvous'Affected if Users or authenticated users have Write or Modify permissions to the installation directory
-
Check for weak permissions on executable filesRun: icacls 'C:\Program Files\TIBCO\Rendezvous\*' | findstr /i "(Users|Everyone) (F|M|W)" to list executables with overly permissive accessAffected if Executable files in the Rendezvous directory grant Write or Full Control to non-privileged users like Users group
A system is affected if TIBCO Rendezvous version 8.5.1 or lower is installed AND non-administrative users have write access to the installation directory or its executable files.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor patch by upgrading TIBCO Rendezvous and TIBCO Rendezvous Developer Edition to version 8.5.1 or later. Until patched, restrict physical/local access to the server, monitor installation directories for unauthorized file modifications, and ensure users lack write access to TIBCO program directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28817 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-28817 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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