# CVE-2014-2716: Weak cryptography in n/a

> Remote attackers can decrypt plaintext messages by exploiting reused RC4 cipher streams in Ekahau RTLS devices.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7hjm-px29-rv4v

## What is CVE-2014-2716?

CVE-2014-2716 is a medium-severity vulnerability in n/a, published on 19 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ekahau B4 staff badge tag 5.7 with firmware 1.4.52, Real-Time Location System (RTLS) Controller 6.0.5-FINAL, and Activator 3 reuses the RC4 cipher stream, which makes it easier for remote attackers to obtain plaintext messages via an XOR operation on two ciphertexts.

Weakness: CWE-310

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

It affects 3 products.


Products: Ekahau Activator, Ekahau B4 Staff Badge Tag Firmware, Ekahau Real-Time Location System Controller.

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

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

## Is CVE-2014-2716 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-9408](https://insights.sbomify.com/CVE-2014-9408/): Weak cryptography in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2716 is a medium-severity vulnerability in n/a, published on 19 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2716 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-2716/ (Markdown: https://insights.sbomify.com/CVE-2014-2716/index.md)
```

## Sources

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

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