# CVE-2014-9406: Hardcoded credentials in n/a

> Remote attackers can gain administrative access to ARRIS Touchstone gateways using the default password, requiring immediate credential changes.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-358p-qq7j-5wh2

## What is CVE-2014-9406?

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

### Official description

ARRIS Touchstone TG862G/CT Telephony Gateway with firmware 7.6.59S.CT and earlier has a default password of password for the admin account, which makes it easier for remote attackers to obtain access via a request to home_loggedout.php.

Weakness: CWE-255

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

It affects 1 product.


Products: Arris Touchstone Tg862g\/Ct Firmware.

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

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

## Is CVE-2014-9406 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5437](https://insights.sbomify.com/CVE-2014-5437/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-5438](https://insights.sbomify.com/CVE-2014-5438/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9406 is a critical vulnerability in n/a, published on 18 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-9406 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-9406/ (Markdown: https://insights.sbomify.com/CVE-2014-9406/index.md)
```

## Sources

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

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