Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
12/9/2015
04:15 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Sea Craft Voyage Data Systems Vulnerable To Tampering, Spying

Remote attackers could snoop on or corrupt the systems that collect and store radar images, vessels' position and speed, and audio recorded in the ships' bridge or engine room.

The researcher who has discovered security weaknesses in satellite communications is now uncovering vulnerabilities in voyage data recorder systems (VDRs) used by cargo ships, cruise ships, and other sea craft. Remote, unauthenticated attackers might exploit the weaknesses to spy on crew's conversations and tamper with "black box" data investigators would use to discover the cause of an accident -- including radar images, the vessel's position and speed, and audio recorded in the ship's bridge or engine room.

Ruben Santamarta, principal security consultant for IOActive, wrote today about his findings from static analysis and QEMU emulation of the Furumu VR-3000 VDR firmware and software.

Although the VDR is the closest thing seacraft have to an aircraft's "black box," it's very different in terms of access controls. An aircraft's system is intended to be tamper-proof, inaccessible by the pilot and the rest of the crew. Conversely, says Santamarta in an interview with Dark Reading, "It [a VDR] shouldn't be used by everybody but technically the VDR belongs to the vessel's owner. So this basically means that the captain and certain members of the crew have to know how to operate it in case of an emergency. It may be locked but still accessible for authorized personnel."

In his blog today, Santamarta notes two prior examples of VDR tampering. In February 2012, two Indian fishermen were shot by Italian marines who said they thought the fishermen were pirates. The incident caused a diplomatic conflict and an investigation into whether what the Italian marines said was true. The VDR recordings on the Italian craft could have substantiated or discredited the marines' claims, but the Indian Times reported "a preliminary probe into the incident found that the VDR was tampered with" and the records corrupted.

The following month, there was a hit-and-run incident off the southern coast of India. Again, VDR files were tampered with, apparently because a member of the crew inserted a pen drive into the device, leading to rewriting of files and loss of voice data.

As Santamarta writes:

From a security perspective, it seems clear VDRs pose a really interesting target. If you either want to spy on a vessel’s activities or destroy sensitive data that may put your crew in a difficult position, VDRs are the key.

Unfortunately, according to Santmarta, in his blog, "almost the entire design [of the VDRs] should be considered insecure." Altogether they contributed to cause a vulnerability he found in the Furumu VR-3000's firmware upgrade process that allows remote, unauthenticated attackers to execute arbitrary commands with root privileges. 

"The design allows unauthenticated users to install a malicious firmware due to multiple weaknesses," says Santamarta, "weak encryption, unsigned firmware files, privileged endpoints and services exposed."

Although the vulnerability can be exploited by "remote" attackers, it is not directly via the Internet. "VDRs are not connected to the Internet (at least, they shouldn't)," says Santamarta. "The remote vector is related to the network onboard. Also, if this network is not properly segmented this may pose an attack vector for malware located in crew laptops or any other personal device."

Santamarta recommends that any data collected from these devices for forensic purposes should be carefully evaluated for signs of tampering.

"There is no standard way to store data [on VDRs] as the only requirement from the [International Maritime Organization] is that manufacturers should provide software to extract and playback the data," says Santamarta. "So each model should be analyzed separately."

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
Virginia a Hot Spot For Cybersecurity Jobs
Jai Vijayan, Contributing Writer,  10/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-14832
PUBLISHED: 2019-10-15
A flaw was found in the Keycloak REST API before version 8.0.0 where it would permit user access from a realm the user was not configured. An authenticated attacker with knowledge of a user id could use this flaw to access unauthorized information or to carry out further attacks.
CVE-2017-10022
PUBLISHED: 2019-10-15
In haml versions prior to version 5.0.0.beta.2, when using user input to perform tasks on the server, characters like < > " ' must be escaped properly. In this case, the ' character was missed. An attacker can manipulate the input to introduce additional attributes, potentially executing ...
CVE-2019-10759
PUBLISHED: 2019-10-15
safer-eval before 1.3.4 are vulnerable to Arbitrary Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.
CVE-2019-10760
PUBLISHED: 2019-10-15
safer-eval before 1.3.2 are vulnerable to Arbitrary Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.
CVE-2019-17397
PUBLISHED: 2019-10-15
In the DoorDash application through 11.5.2 for Android, the username and password are stored in the log during authentication, and may be available to attackers via logcat.