CVE-2011-0649
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 · uneditedMultiple unspecified vulnerabilities in TIBCO Rendezvous 8.2.1 through 8.3.0, Enterprise Message Service (EMS) 5.1.0 through 6.0.0, Runtime Agent (TRA) 5.6.2 through 5.7.0, Silver BPM Service before 1.0.4, Silver CAP Service vebefore 1.0.2, and Silver BusinessWorks Service 1.0.0, when running on Unix systems, allow local users to gain root privileges via unknown vectors related to SUID and (1) Rendezvous Routing Daemon (rvrd), (2) Rendezvous Secure Daemon (rvsd), (3) Rendezvous Secure Routing Daemon (rvsrd), and (4) EMS Server (tibemsd).
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 confidenceLocal privilege escalation vulnerability in multiple TIBCO products on Unix systems where SUID binaries (rvrd, rvsd, rvsrd, tibemsd) contain unspecified flaws allowing authenticated local users to gain root 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.2.1= 8.3.0= 5.1.0= 5.1.1= 6.0.0= 5.6.2= 5.7.0<= 1.0.3= 1.0.1<= 1.0.1= 1.0.0= 1.0.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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 installed TIBCO productsSearch for TIBCO installation directories (common paths: /opt/tibco, /usr/local/tibco, or $TIBCO_HOME) and list installed product componentsAffected if No TIBCO products are found - not affected
-
Check TIBCO Rendezvous versionLocate the rvrd, rvsd, or rvsrd binaries in the TIBCO installation (typically in <tibco_home>/tibrv/bin/) and query version (e.g., run with --version or check product documentation for version file)Affected if Version is 8.2.1 or 8.3.0 AND SUID bit is set on binary
-
Check TIBCO EMS versionLocate the tibemsd binary (typically in <tibco_home>/ems/bin/) and query versionAffected if Version is 5.1.0, 5.1.1, or 6.0.0 AND SUID bit is set on binary
-
Check TIBCO Runtime Agent versionLocate TRA components and determine version from installation directory or version fileAffected if Version is 5.6.2 or 5.7.0 AND contains SUID binaries rvrd/rvsd/rvsrd
-
Verify SUID bit on vulnerable binariesRun 'ls -la <tibco_home>/*/bin/rvrd <tibco_home>/*/bin/rvsd <tibco_home>/*/bin/rvsrd <tibco_home>/ems/bin/tibemsd 2>/dev/null' to check for 's' in owner permissions (e.g., -rwsr-xr-x)Affected if Any of the four binaries (rvrd, rvsd, rvsrd, tibemsd) have the SUID bit set (owner permissions show 's' instead of 'x')
Affected if any TIBCO product matching the specific versions (Rendezvous 8.2.1/8.3.0, EMS 5.1.0/5.1.1/6.0.0, TRA 5.6.2/5.7.0, Silver services 1.0.0-1.0.3) is installed AND the SUID binaries (rvrd, rvsd, rvsrd, tibemsd) have the SUID bit enabled.
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 patches for affected TIBCO products (Rendezvous, EMS, TRA, Silver services) to patched versions, or remove SUID bits from affected binaries using 'chmod -s' if patching is not immediately feasible.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0649 — 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-2011-0649 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