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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: George has not accepted that the technology age has come to an end.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23351
PUBLISHED: 2021-03-08
The package github.com/pires/go-proxyproto before 0.5.0 are vulnerable to Denial of Service (DoS) via the parseVersion1() function. The reader in this package is a default bufio.Reader wrapping a net.Conn. It will read from the connection until it finds a newline. Since no limits are implemented in ...
CVE-2009-20001
PUBLISHED: 2021-03-07
An issue was discovered in MantisBT before 2.24.5. It associates a unique cookie string with each user. This string is not reset upon logout (i.e., the user session is still considered valid and active), allowing an attacker who somehow gained access to a user's cookie to login as them.
CVE-2020-28466
PUBLISHED: 2021-03-07
This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers: Running a NATS service which is exposed to untrusted users presents a heightened r...
CVE-2021-27364
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.
CVE-2021-27365
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. Certain iSCSI data structures do not have appropriate length constraints or checks, and can exceed the PAGE_SIZE value. An unprivileged user can send a Netlink message that is associated with iSCSI, and has a length up to the maximum length...