# CVE-2018-5266: Information disclosure in n/a

> Remote attackers can obtain valid usernames and default credentials from Cobham Sea Tel devices, facilitating unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5wp8-cmr8-3522

## What is CVE-2018-5266?

CVE-2018-5266 is a high-severity vulnerability in n/a, published on 8 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cobham Sea Tel 121 build 222701 devices allow remote attackers to obtain potentially sensitive information about valid usernames by reading the loginName lines at the js/userLogin.js URI. NOTE: default passwords for the standard usernames are listed in the product's documentation: Dealer with password seatel3, SysAdmin with password seatel2, and User with password seatel1.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Cobham Sea Tel 121 Firmware.

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

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

## Is CVE-2018-5266 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-5267](https://insights.sbomify.com/CVE-2018-5267/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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