Cobham Sailor satellite terminals contain hardcoded credentials

2014-08-07T00:00:00
ID VU:460687
Type cert
Reporter CERT
Modified 2014-08-14T03:05:00

Description

Overview

Cobham Sailor 900 and 6000 series satellite terminals contain hardcoded credentials.

Description

CWE-798: Use of Hard-coded Credentials

IOActive reports that Cobham Sailor 900 and 6000 series satellite communication terminals running firmware version: 1.08 MFHF / 2.11 VHF contain hardcoded administrator credentials.

The vendor Cobham has provided the following statement:
_Cobham SATCOM has found that potential exploitation of the vulnerabilities presented requires either physical access to the equipment or connectivity to the maintenance part of the network, which also requires a physical presence at the terminal. Specifically, in the maritime world, there are very strict requirements for equipment installation and physical access to the equipment is restricted to authorized personnel. _

_All Cobham network devices are part of a network with a very specific network topology. Equipment and network devices are segregated into clear network segments with different access levels. Maintenance of Cobham network devices is usually carried out by equipment that is physically connected to the network device itself (maintenance port) or connected to an Ethernet switch within a protected network segment. From a network security perspective, Cobham devices can therefore only be subject to attacks if the attacker has either physical access to the device or segment or the network has been installed incorrectly. _

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


Impact

A remote unauthenticated attacker may be able to gain full control over the device.


Solution

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


Vendor Information

460687

Filter by status: All Affected Not Affected Unknown

Filter by content: __ Additional information available

__ Sort by: Status Alphabetical

Expand all

Javascript is disabled. Click here to view vendors.

Cobham plc __ Affected

Notified: January 14, 2014 Updated: August 05, 2014

Status

Affected

Vendor Statement

Cobham SATCOM has found that potential exploitation of the vulnerabilities presented requires either physical access to the equipment or connectivity to the maintenance part of the network, which also requires a physical presence at the terminal.

Specifically, in the maritime world, there are very strict requirements for equipment installation and physical access to the equipment is restricted to authorized personnel.

All Cobham network devices are part of a network with a very specific network topology. Equipment and network devices are segregated into clear network segments with different access levels.

Maintenance of Cobham network devices is usually carried out by equipment that is physically connected to the network device itself (maintenance port) or connected to an Ethernet switch within a protected network segment.
From a network security perspective, Cobham devices can therefore only be subject to attacks if the attacker has either physical access to the device or segment or the network has been installed incorrectly.

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

Vendor Information

We are not aware of further vendor information regarding this vulnerability.

CVSS Metrics

Group | Score | Vector
---|---|---
Base | 10 | AV:N/AC:L/Au:N/C:C/I:C/A:C
Temporal | 8.1 | E:POC/RL:ND/RC:UC
Environmental | 2.0 | CDP:N/TD:L/CR:ND/IR:ND/AR:ND

References

  • <http://www.cobham.com/about-cobham/aerospace-and-security/about-us/satcom/satellite-communication-at-sea/products-and-services/inmarsat-fleetbroadband.aspx>
  • <http://cwe.mitre.org/data/definitions/798.html>

Acknowledgements

Thanks to Ruben Santamarta for reporting this vulnerability.

This document was written by Chris King.

Other Information

CVE IDs: | CVE-2014-2940
---|---
Date Public: | 2014-08-07
Date First Published: | 2014-08-07
Date Last Updated: | 2014-08-14 03:05 UTC
Document Revision: | 10