9.3 High
CVSS2
Attack Vector
NETWORK
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:C/I:C/A:C
0.004 Low
EPSS
Percentile
72.9%
Cobham’s thraneLINK protocol does not verify cryptographic signatures for firmware updates before installing them. This may allow an attacker to deploy a malicious firmware update to the device.
CWE-347: Improper Verification of Cryptographic Signature
IOActive reports that Cobham’s thraneLINK protocol does not verify cryptographic signatures for firmware updates before installing them. A remote unauthenticated attacker may use the SLPFindSrvs
protocol function to discover thraneLINK devices on the network then send a crafted SNMP request to have the device download a firmware update from a TFTP server under the control of the attacker.
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 aeronautical and 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.
A remote unauthenticated attacker may be able to deploy a malicious firmware image to a thraneLINK device and execute arbitrary code.
We are currently unaware of a practical solution to this problem. Please consider the following workaround.
Restrict Access
Enable firewall rules that restrict TFTP access to only trusted sources for thraneLINK devices. To stop an attacker from discovering thraneLINK devices, block broadcast requests for UDP port 427 to thraneLINK devices from untrusted sources.
179732
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.
Notified: January 14, 2014 Updated: July 28, 2014
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: January 14, 2014 Updated: August 05, 2014
Affected
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 aeronautical and 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.
We are not aware of further vendor information regarding this vulnerability.
Group | Score | Vector |
---|---|---|
Base | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Temporal | 6.8 | E:U/RL:W/RC:UC |
Environmental | 5.1 | CDP:ND/TD:M/CR:ND/IR:ND/AR:ND |
Thanks to Ruben Santamarta for reporting this vulnerability.
This document was written by Chris King.
CVE IDs: | CVE-2014-0328 |
---|---|
Date Public: | 2014-08-07 Date First Published: |