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

> Attackers can gain administrative privileges on Foxconn LTE access points by exploiting a weak default password and insecure cookie-based authentication mechanisms.

- **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:** 10 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4r4r-hj2w-xx29

## What is CVE-2018-9112?

CVE-2018-9112 is a critical vulnerability in n/a, published on 10 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A low privileged admin account with a weak default password of admin exists on the Foxconn FEMTO AP-FC4064-T AP_GT_B38_5.8.3lb15-W47 LTE Build 15. In addition, its web management page relies on the existence or values of cookies when performing security-critical operations. One can gain privileges by modifying cookies.

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

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

It affects 1 product.


Products: Foxconn Ap-Fc4064-T Firmware.

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

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

## Is CVE-2018-9112 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-6312](https://insights.sbomify.com/CVE-2018-6312/): Hardcoded credentials in n/a (high 7.2)
- [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-9112 and fix it if it is affected.

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

## Sources

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

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