CVE-2013-6034
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMultiple satellite terminal devices (GateHouse, Harris BGAN, Hughes Network Systems 9201/9450/9502, Inmarsat, Japan Radio JUE-250/500, Thuraya IP) contain hardcoded credentials embedded in their firmware, allowing attackers to obtain unauthorized login access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions= rf-7800b-du204= rf-7800b-vu204all versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify affected satellite terminal devices in your networkInventory all network devices and satellite terminals. Look for GateHouse, Harris BGAN (rf-7800b-du204, rf-7800b-vu204), Hughes 9201/9450/9502, Inmarsat, Japan Radio JUE-250/500 terminals. Check device labels, management interfaces, or network scans for model numbers.Affected if Any of the listed device models (GateHouse, Harris BGAN, Hughes 9201/9450/9502, Inmarsat, Japan Radio JUE-250/500) are present in the environment.
-
Determine if default credentials are still in useConsult the vendor documentation for default login credentials. Attempt to authenticate to the device management interface using the known default username/password combinations for the specific model. Alternatively, check if credentials have been changed from vendor defaults in any credential databases or configuration management systems.Affected if The default vendor credentials have not been changed, or the hardcoded credentials embedded in firmware still provide access.
-
Verify management interface accessibilityCheck network segmentation and firewall rules. Determine if the satellite terminal management interfaces (typically HTTP/HTTPS on ports 80/443 or telnet/ssh on ports 22/23) are accessible from untrusted networks, the internet, or non-administrative network segments. Use network scans to identify exposed management interfaces.Affected if The device management interface is exposed to untrusted networks or the internet without proper access controls.
You are affected if you have any of the listed satellite terminal devices (GateHouse, Harris BGAN, Hughes 9201/9450/9502, Inmarsat, Japan Radio JUE-250/500) and the hardcoded default credentials have not been changed or the management interface is accessible to unauthorized users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace or update firmware to vendor-patched versions; if unavailable, implement network segmentation, change default credentials if possible, and restrict access to management interfaces.
- Consultation12.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6034 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-6034 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data