# CVE-2014-2543: Memory corruption in n/a

> Remote attackers with client access can execute arbitrary code via buffer overflow in TIBCO Rendezvous daemons.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q2vf-jgqw-hc46

## What is CVE-2014-2543?

CVE-2014-2543 is a high-severity memory corruption vulnerability in n/a, published on 8 Apr 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in the Rendezvous Daemon (rvd), Rendezvous Routing Daemon (rvrd), Rendezvous Secure Daemon (rvsd), and Rendezvous Secure Routing Daemon (rvsrd) in TIBCO Rendezvous before 8.4.2, Messaging Appliance before 8.7.1, and Substation ES before 2.8.1 allows remote attackers to execute arbitrary code by leveraging access to a directly connected client and transmitting crafted data.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2014-2543?

It affects 3 products.


Products: Tibco Messaging Appliance, Tibco Rendezvous, Tibco Substantiation Es.

## How do I fix CVE-2014-2543?

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

## Is CVE-2014-2543 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-4555](https://insights.sbomify.com/CVE-2015-4555/): Memory corruption in n/a (high 7.5)
- [CVE-2014-2541](https://insights.sbomify.com/CVE-2014-2541/): Missing authorization in n/a (medium 5.0)
- [CVE-2014-2542](https://insights.sbomify.com/CVE-2014-2542/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2543 and fix it if it is affected.

What it is: CVE-2014-2543 is a high-severity memory corruption vulnerability in n/a, published on 8 Apr 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2543 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-2014-2543/ (Markdown: https://insights.sbomify.com/CVE-2014-2543/index.md)
```

## Sources

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

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