Vulnerability Note VU#820196

Furuno Voyage Data Recorder (VDR) moduleserv firmware update utility fails to properly sanitize user-provided input

Original Release date: 04 Jan 2016 | Last revised: 04 Jan 2016


Furuno Voyage Data Recorder (VDR) VR-3000/VR-3000S and VR-7000 moduleserv firmware update utility fails to properly sanitize user-provided input and is vulnerable to arbitrary command execution with root privileges.


According to the Furuno VDR product page, the VDR "records all crucial data to identify the cause of maritime casualty as well as contribute to the future prevention of the catastrophe of any kind."

Multiple versions of Furuno VDR VR-3000/VR-3000S and VR-7000 contain a firmware update utility called moduleserv that listens on TCP port 10110. The moduleserv service fails to properly sanitize user-provided input, which an unauthenticated attacker may leverage to execute arbitrary commands with root privileges. For more information, refer to the blog post by IOActive.


An unauthenticated attacker with network access to affected devices can execute arbitrary commands with root privileges.


Apply an update

The vendor has released updates to address this vulnerability. Updates should be applied as follows.

For the VR-3000/VR-3000S:

  • V1.50 through V1.54 should be updated to V1.56
  • V1.61 should be updated to V1.62
  • V2.06 through V2.54 should be updated to V2.56
  • V2.60 through V2.61 should be updated to V2.62
For the VR-7000:
  • V1.02 should be updated to V1.04

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
FurunoAffected-22 Dec 2015
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base 8.3 AV:A/AC:L/Au:N/C:C/I:C/A:C
Temporal 6.2 E:POC/RL:OF/RC:UR
Environmental 1.8 CDP:LM/TD:L/CR:ND/IR:ND/AR:ND



Thanks to Ruben Santamarta of IOActive for reporting this vulnerability. Thanks to JPCERT/CC for coordinating with the vendor.

This document was written by Joel Land.

Other Information

  • CVE IDs: Unknown
  • Date Public: 04 Jan 2015
  • Date First Published: 04 Jan 2016
  • Date Last Updated: 04 Jan 2016
  • Document Revision: 24


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