# CVE-2011-0649: Privilege escalation in n/a

> Local attackers can gain root privileges on Unix systems via SUID binaries in TIBCO Rendezvous and EMS components.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hwqv-g52g-rgvm

## What is CVE-2011-0649?

CVE-2011-0649 is a high-severity vulnerability in n/a, published on 4 Feb 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple 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).

## Which versions are affected by CVE-2011-0649?

It affects 6 products.


Products: Tibco Enterprise Message Service, Tibco Rendezvous, Tibco Runtime Agent, Tibco Silver Bpm Service, Tibco Silver Businessworks Service, Tibco Silver Cap Service.

## How do I fix CVE-2011-0649?

No fix has been published for CVE-2011-0649 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-0649 being exploited?

There is no known exploitation of CVE-2011-0649 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2009-1291](https://insights.sbomify.com/CVE-2009-1291/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-1704](https://insights.sbomify.com/CVE-2008-1704/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5655](https://insights.sbomify.com/CVE-2007-5655/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5656](https://insights.sbomify.com/CVE-2007-5656/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5657](https://insights.sbomify.com/CVE-2007-5657/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0649 and fix it if it is affected.

What it is: CVE-2011-0649 is a high-severity vulnerability in n/a, published on 4 Feb 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-0649 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-0649/ (Markdown: https://insights.sbomify.com/CVE-2011-0649/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-0649
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-0649
- OSV: https://osv.dev/vulnerability/CVE-2011-0649

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-0649/
Summaries are generated and may contain mistakes; the official description above is the record.