# CVE-2013-6034: Hardcoded credentials in n/a

> Hardcoded credentials in satellite terminal firmware allow attackers to gain unauthorized login access without user interaction.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6qh6-vf88-qc9j

## What is CVE-2013-6034?

CVE-2013-6034 is a critical vulnerability in n/a, published on 4 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The firmware on GateHouse; Harris BGAN RF-7800B-VU204 and BGAN RF-7800B-DU204; Hughes Network Systems 9201, 9450, and 9502; Inmarsat; Japan Radio JUE-250 and JUE-500; and Thuraya IP satellite terminals has hardcoded credentials, which makes it easier for attackers to obtain unspecified login access via unknown vectors.

Weakness: CWE-255

## Which versions are affected by CVE-2013-6034?

It affects 9 products.


Products: Gatehouse Gatehouse, Harris Bgan, Hughes Network Systems 9201, Hughes Network Systems 9450, Hughes Network Systems 9502, Inmarsat Inmarsat, Japan Radio Jue-250, Japan Radio Jue-500, Thuraya Telecommunications Ip.

## How do I fix CVE-2013-6034?

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

## Is CVE-2013-6034 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6035](https://insights.sbomify.com/CVE-2013-6035/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6034 and fix it if it is affected.

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

## Sources

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

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