CVE-2013-6035
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 does not require authentication for sessions on TCP port 1827, which allows remote attackers to execute arbitrary code via unspecified protocol operations.
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 · high confidenceMultiple BGAN satellite terminal devices from various manufacturers (GateHouse, Harris, Hughes, Inmarsat, Japan Radio, Thuraya) have firmware with an unauthenticated service running on TCP port 1827. This allows remote attackers to execute arbitrary code without any credentials.
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 BGAN terminal deviceCheck the device model and manufacturer. Look for model numbers matching: RF-7800B-DU204, RF-7800B-VU204 (Harris), 9201, 9450, 9502 (Hughes), Jue 250, Jue 500 (Japan Radio), or Gatehouse/Inmarsat/Thuraya BGAN devices. Use device documentation, web interface, or SNMP queries to confirm the exact model.Affected if The device is a BGAN satellite terminal from any of the listed manufacturers (GateHouse, Harris, Hughes, Inmarsat, Japan Radio, Thuraya).
-
Scan for open TCP port 1827Run a network port scan against the target device using nmap (nmap -p 1827 <target-ip>) or similar tool. Verify that TCP port 1827 is listening and accepting connections.Affected if TCP port 1827 is open and responding on the target device.
-
Test for unauthenticated service accessAttempt to connect to TCP port 1827 using a network client such as netcat (nc -nv <target-ip> 1827) or telnet. Observe whether the connection succeeds and returns any prompt or response without requiring login credentials.Affected if A connection to port 1827 succeeds and provides access or a prompt without any authentication credentials.
-
Verify network accessibilityDetermine whether the device with port 1827 exposed is accessible from untrusted networks. Review firewall rules, NAT configurations, and network segmentation to confirm whether the management interface is exposed to the internet or untrusted LAN segments.Affected if The device with port 1827 is reachable from networks outside the trusted administrative zone.
The environment is affected if a BGAN satellite terminal from the listed manufacturers has TCP port 1827 open and accessible, allowing unauthenticated connections that could enable remote code execution.
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 dataImplement network segmentation and firewall rules to restrict access to TCP port 1827 on affected devices. Contact device vendors for available firmware patches.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6035 — 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-6035 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