# CVE-2018-6312: Hardcoded credentials in n/a

> A weak default password allows attackers to enable Telnet and gain root access, leading to full system compromise and data disclosure.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5vvc-wv25-82fx

## What is CVE-2018-6312?

CVE-2018-6312 is a high-severity vulnerability in n/a, published on 10 Mar 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A privileged account with a weak default password on the Foxconn femtocell FEMTO AP-FC4064-T version AP_GT_B38_5.8.3lb15-W47 LTE Build 15 can be used to turn on the TELNET service via the web interface, which allows root login without any password. This vulnerability will lead to full system compromise and disclosure of user communications. The foxconn account with an 8-character lowercase alphabetic password can be used.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2018-6312?

It affects 1 product.


Products: Foxconn Ap-Fc4064-T Firmware.

## How do I fix CVE-2018-6312?

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

## Is CVE-2018-6312 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-9112](https://insights.sbomify.com/CVE-2018-9112/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-6311](https://insights.sbomify.com/CVE-2018-6311/): Missing authorization in n/a (medium 6.8)
- [CVE-2018-9111](https://insights.sbomify.com/CVE-2018-9111/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6312 and fix it if it is affected.

What it is: CVE-2018-6312 is a high-severity vulnerability in n/a, published on 10 Mar 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-6312 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-2018-6312/ (Markdown: https://insights.sbomify.com/CVE-2018-6312/index.md)
```

## Sources

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

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