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

> Remote attackers can sniff unencrypted network traffic to steal Active Directory credentials when specific wireless features are enabled.

- **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:** 15 Jan 2015
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-g5q6-q8j3-6m3c

## What is CVE-2014-9596?

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

### Official description

Panasonic Arbitrator Back-End Server (BES) MK 2.0 VPU before 9.3.1 build 4.08.003.0, when USB Wi-Fi or Direct LAN is enabled, and MK 3.0 VPU before 9.3.1 build 5.06.000.0, when Embedded Wi-Fi or Direct LAN is enabled, does not use encryption, which allows remote attackers to obtain sensitive information by sniffing the network for client-server traffic, as demonstrated by Active Directory credential information.

Weakness: CWE-310

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

It affects 4 products.


Products: Panasonic Arbitrator Back-End Server Mk 2.0 Vpu, Panasonic Arbitrator Back-End Server Mk 2.0 Vpu Firmware, Panasonic Arbitrator Back-End Server Mk 3.0 Vpu, Panasonic Arbitrator Back-End Server Mk 3.0 Vpu Firmware.

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

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

## Is CVE-2014-9596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9596 is a medium-severity vulnerability in n/a, published on 15 Jan 2015. 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-9596 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-9596/ (Markdown: https://insights.sbomify.com/CVE-2014-9596/index.md)
```

## Sources

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

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