CVE-2021-35500
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 Data Virtualization Server component of TIBCO Software Inc.'s TIBCO Data Virtualization, TIBCO Data Virtualization, TIBCO Data Virtualization, and TIBCO Data Virtualization for AWS Marketplace contains a difficult to exploit vulnerability that allows a low privileged attacker with local access to download arbitrary files outside of the scope of the user's permissions on the affected system. Affected releases are TIBCO Software Inc.'s TIBCO Data Virtualization: versions 8.3.0 and below, TIBCO Data Virtualization: version 8.4.0, TIBCO Data Virtualization: version 8.5.0, and TIBCO Data Virtualization for AWS Marketplace: versions 8.5.0 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 confidenceTIBCO Data Virtualization Server contains a local file download vulnerability where a low-privileged attacker with local system access can bypass authorization controls to download arbitrary files outside their permitted scope. The flaw allows unauthorized file system access through the Data Virtualization component, representing a privilege escalation/authorization failure.
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.3.0= 8.4.0= 8.5.0<= 8.5.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify TIBCO Data Virtualization installationSearch for TDV installation directories such as /opt/tibco, /opt/TIBCO, or C:\TIBCO on the local system. Look for directories containing 'DataVirtualization' or 'tdv' in the name.Affected if TIBCO Data Virtualization software is installed on the system
-
Determine installed TDV versionLocate and read the version file or check the product version. Common locations include version.txt in the installation root, or run: cd <installation_dir>/tdv && ./tdvversion (or tdvversion.bat on Windows).Affected if The installed version cannot be determined or is not clearly displayed
-
Compare version against affected rangesReview the discovered version against the affected ranges: versions <= 8.3.0, version 8.4.0, and version 8.5.0 are vulnerable. Note that version 8.4.1 and above may be patched.Affected if The installed version is 8.3.0 or lower, exactly 8.4.0, or exactly 8.5.0
-
Verify Data Virtualization component is activeCheck if the TDV server service or process is running. On Linux: ps aux | grep -i tdv. On Windows: Check services named 'TIBCO Data Virtualization' or look for processes like tdvserver.exe.Affected if The TDV server component is actively running
The environment is affected if TIBCO Data Virtualization is installed with version 8.3.0 or lower, 8.4.0, or 8.5.0 and the Data Virtualization server component is actively running.
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 vendor-provided patches for affected TIBCO Data Virtualization versions (8.3.0 and below, 8.4.0, 8.5.0). Until patched, restrict local system access strictly and monitor for unauthorized file access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2021-35500 — 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-35500 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