# CVE-2017-14115: Hardcoded credentials in n/a

> Remote attackers can gain root access via hardcoded SSH credentials on AT&T U-verse gateways when IP Passthrough is disabled.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 3 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9pg3-r76h-43mh

## What is CVE-2017-14115?

CVE-2017-14115 is a high-severity vulnerability in n/a, published on 3 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AT&T U-verse 9.2.2h0d83 firmware for the Arris NVG589 and NVG599 devices, when IP Passthrough mode is not used, configures ssh-permanent-enable WAN SSH logins to the remotessh account with the 5SaP9I26 password, which allows remote attackers to access a "Terminal shell v1.0" service, and subsequently obtain unrestricted root privileges, by establishing an SSH session and then entering certain shell metacharacters and BusyBox commands.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2017-14115?

It affects 1 product.


Products: Att U-Verse Firmware.

## How do I fix CVE-2017-14115?

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

## Is CVE-2017-14115 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-10793](https://insights.sbomify.com/CVE-2017-10793/): Hardcoded credentials in n/a (high 8.1)
- [CVE-2017-14116](https://insights.sbomify.com/CVE-2017-14116/): Hardcoded credentials in n/a (high 8.1)
- [CVE-2017-14117](https://insights.sbomify.com/CVE-2017-14117/): Missing authorization in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14115 and fix it if it is affected.

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

## Sources

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

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