CVE-2013-7180
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 · uneditedCobham SAILOR 900 VSAT; SAILOR FleetBroadBand 150, 250, and 500; EXPLORER BGAN; and AVIATOR 200, 300, 350, and 700D devices do not properly restrict password recovery, which allows attackers to obtain administrative privileges by leveraging physical access or terminal access to spoof a reset code.
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 Cobham SAILOR satellite communication devices contain a password recovery mechanism that does not properly validate reset codes. An attacker with physical access to the device or terminal access can spoof a password reset code to bypass authentication and gain full administrative privileges.
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 versionsall versionsall 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/I:N/A:N
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 the device modelAccess the device management interface or check the physical device label to confirm the exact model (e.g., Aviator 200, Aviator 300, Aviator 350, Aviator 700d, Explorer Bgan, Sailor 900 Vsat, Sailor Fleetbroadband 150, or Sailor Fleetbroadband 250).Affected if The device is any of the Cobham models listed in the affected products (Aviator 200, 300, 350, 700d, Explorer Bgan, Sailor 900 Vsat, Fleetbroadband 150, or 250).
-
Determine if console or terminal access is enabledCheck the device network configuration and physical ports to see if a command-line interface, telnet, SSH, or serial console is accessible over the network or locally.Affected if Console, telnet, SSH, or serial terminal access is exposed on the device.
-
Assess physical access exposureInspect the physical location of the device to determine if unauthorized individuals can access the device console ports or control panel.Affected if Physical access to the device console ports or terminals is possible by unauthorized persons.
-
Verify password reset mechanism availabilityAttempt to access the password recovery or reset function through the console/terminal interface, or review device documentation for the reset code procedure.Affected if The password reset mechanism is accessible via console or terminal and accepts reset codes without proper validation.
If the device is any of the affected Cobham models (Aviator, Explorer Bgan, Sailor 900, or Fleetbroadband series) and console/terminal or physical access is exposed, the environment is vulnerable to CVE-2013-7180.
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 physical access controls to prevent unauthorized access to device console/terminals; contact vendor for firmware updates that address the improper password recovery mechanism; if no update available, consider network segmentation and monitoring of terminal access.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7180 — 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-7180 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