dbcve.org
Aviator 700dHardware / appliance · Cobham

CVE-2014-2964

MEDIUM · 6.9 CVSS v2.0 Published 2014-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Cobham Aviator 700D and 700E satellite terminals have hardcoded passwords for the (1) debug, (2) prod, (3) do160, and (4) flrp programs, which allows physically proximate attackers to gain privileges by sending a password over a serial line.

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 confidence

The Cobham Aviator 700D and 700E satellite terminals contain hardcoded passwords embedded in firmware for four separate programs (debug, prod, do160, and flrp). An attacker with physical proximity to the device and access to the serial interface can authenticate using these static credentials to obtain elevated privileges on the terminal.

Mitigation物理的なシリアルインターフェースへのアクセスを制限し、ベンダー提供的ファームウェアアップデートを適用してハードコードされた認証情報を変更する必要があります。

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 data
Aviator 700dHardware / appliance
Affected:all versions
Aviator 700eHardware / appliance
Affected:all versions

CVSS 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
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:M/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the satellite terminal model
    Check the device label, management interface, or serial console boot output for the exact model number (Aviator 700D or Aviator 700E)
    Affected if The model is Cobham Aviator 700D or Cobham Aviator 700E
  2. Confirm all firmware versions are affected
    Since vendor states all versions are affected, verify the installed firmware version via the serial console or management interface if accessible
    Affected if Any firmware version is running on Aviator 700D or 700E (all versions are vulnerable)
  3. Assess physical access to serial interface
    Examine the device deployment location and enclosure to determine if an attacker could obtain physical proximity and access the RS-232 serial port
    Affected if The serial interface is physically accessible to unauthorized persons

If you have deployed Cobham Aviator 700D or 700E terminals with accessible serial interfaces, you are affected by hardcoded credential vulnerability CVE-2014-2964.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

物理的なシリアルインターフェースへのアクセスを制限し、ベンダー提供的ファームウェアアップデートを適用してハードコードされた認証情報を変更する必要があります。

Fix this in Aviator 700d Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-2964 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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