# CVE-2018-6311: Missing authorization in n/a

> Attackers with physical access can gain root privileges via UART pins, leading to full system compromise and user data disclosure.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4f6w-v2mv-qm2r

## What is CVE-2018-6311?

CVE-2018-6311 is a medium-severity missing authorization vulnerability in n/a, published on 10 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

One can gain root access on the Foxconn femtocell FEMTO AP-FC4064-T version AP_GT_B38_5.8.3lb15-W47 LTE Build 15 via UART pins without any restrictions, which leads to full system compromise and disclosure of user communications.

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

It affects 1 product.


Products: Foxconn Ap-Fc4064-T Firmware.

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

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

## Is CVE-2018-6311 being exploited?

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

What it is: CVE-2018-6311 is a medium-severity missing authorization vulnerability in n/a, published on 10 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-6311 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-6311/ (Markdown: https://insights.sbomify.com/CVE-2018-6311/index.md)
```

## Sources

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

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