Vulnerability Note VU#269991

Cobham Sailor 6000 series satellite terminal contain hardcoded credentials

Original Release date: 07 Aug 2014 | Last revised: 13 Aug 2014


Cobham Sailor 6000 series satellite terminals contain hardcoded credentials for communicating via the Tbus 2 protocol.


Note: this is a different vulnerability from VU#460687

CWE-798: Use of Hard-coded Credentials
IOActive reports that Cobham Sailor 6000 series satellite communication terminals contain hardcoded credentials to communicate via the Tbus 2 protocol. The Tbus 2 protocol is a maintenance protocol for shipboard communications.

The vendor Cobham has provided the following statement:
All Over-The-Air (OTA) commands require user authentication based on specific passwords to the specific terminal. No hard-coded credentials can be used in any case. User authentication is required for each individual command set so there is no possibility to exploit another user’s credentials. Furthermore the security has been enhanced in mini-C software release 1.06 by requiring local action on the ship before allowing remote TBUS2 commands.

Cobham SATCOM will continue to evaluate any potential vulnerabilities with its equipment and implement increased security measures if required.


An unauthenticated attacker may be able to send arbitrary Tbus 2 commands to the terminal, affecting the operation of the system.


The CERT/CC is currently unaware of a practical solution to this problem.

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
Cobham plcAffected14 Jan 201428 Jul 2014
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base 7.1 AV:N/AC:M/Au:N/C:N/I:C/A:N
Temporal 5.8 E:POC/RL:U/RC:UC
Environmental 1.4 CDP:N/TD:L/CR:ND/IR:ND/AR:ND



Thanks to Ruben Santamarta for reporting this vulnerability.

This document was written by Chris King.

Other Information

  • CVE IDs: CVE-2014-2941
  • Date Public: 07 Aug 2014
  • Date First Published: 07 Aug 2014
  • Date Last Updated: 13 Aug 2014
  • Document Revision: 9


If you have feedback, comments, or additional information about this vulnerability, please send us email.