# CVE-2016-2364: Hardcoded credentials in n/a

> Remote attackers can defeat cryptographic protections in the Fonality HUDweb plugin by using a shared hardcoded private key found in other installations.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 20 Jun 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cwhh-p654-4p5p

## What is CVE-2016-2364?

CVE-2016-2364 is a high-severity vulnerability in n/a, published on 20 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Chrome HUDweb plugin before 2016-05-05 for Fonality (previously trixbox Pro) 12.6 through 14.1i uses the same hardcoded private key across different customers' installations, which allows remote attackers to defeat cryptographic protection mechanisms by leveraging knowledge of this key from another installation.

Weakness: CWE-310

## Which versions are affected by CVE-2016-2364?

It affects 2 products.


Products: Fonality Fonality, Fonality Hud Web.

## How do I fix CVE-2016-2364?

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

## Is CVE-2016-2364 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-2362](https://insights.sbomify.com/CVE-2016-2362/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2016-2363](https://insights.sbomify.com/CVE-2016-2363/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2364 and fix it if it is affected.

What it is: CVE-2016-2364 is a high-severity vulnerability in n/a, published on 20 Jun 2016. 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-2016-2364 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-2016-2364/ (Markdown: https://insights.sbomify.com/CVE-2016-2364/index.md)
```

## Sources

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

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