# CVE-2014-2941: Hardcoded credentials in n/a

> Remote attackers can access Cobham Sailor 6000 satellite terminals using hardcoded credentials, potentially compromising data and control.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:C/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:** 15 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pr8m-pgmq-mj9q

## What is CVE-2014-2941?

CVE-2014-2941 is a high-severity vulnerability in n/a, published on 15 Aug 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cobham Sailor 6000 satellite terminals have hardcoded Tbus 2 credentials, which allows remote attackers to obtain access via a TBUS2 command.  NOTE: the vendor reportedly states "there is no possibility to exploit another user's credentials.

## Which versions are affected by CVE-2014-2941?

It affects 4 products.


Products: Cobham Ailor 6110 Mini-C Gmdss, Cobham Sailor 6006 Message Terminal, Cobham Sailor 6222 Vhf, Cobham Sailor 6300 Mf \/ Hf.

## How do I fix CVE-2014-2941?

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

## Is CVE-2014-2941 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0328](https://insights.sbomify.com/CVE-2014-0328/): Security feature bypass in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2941 and fix it if it is affected.

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

## Sources

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

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