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

> Remote attackers can gain unauthorized access to Fonality systems via FTP or SSH using hardcoded credentials, compromising data and system integrity.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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-m9hq-6jrr-f23g

## What is CVE-2016-2362?

CVE-2016-2362 is a critical 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

Fonality (previously trixbox Pro) 12.6 through 14.1i before 2016-06-01 has a hardcoded password for the FTP account, which allows remote attackers to obtain access via a (1) FTP or (2) SSH connection.

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

It affects 1 product.


Products: Fonality Fonality.

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

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

## Is CVE-2016-2362 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-2362 is a critical 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-2362 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-2362/ (Markdown: https://insights.sbomify.com/CVE-2016-2362/index.md)
```

## Sources

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

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