Skip to main content

NFS Exported Filesystems List Vulnerability Reported for Delphix Continuous Data Platform (KBA9363)




KBA# 9363



In the process of security auditing or scanning, an "NFS Exported Filesystems List Vulnerability" may be reported for the Continuous Data Engine. This article is intended to speak to this concern.

The finding may be reported by various network security tools such as Qualys, QID 66002, and may read as follows:

This system is running a Network File System (NFS) server that enables a remote host to access and share files and directories. The current configuration of this system gives both authorized and unauthorized users the list of exported disks and authorized hosts.

NFS Exported Filesystems List Vulnerability

If the NFS server is not required on this system, then shutdown and disable the mountd and nfsd RPC services.

If the NFS server is required on this system, then the solution is not as simple. Since the server's clients need to be able to access the export list, this service cannot be shutdown.  Access can be restricted to hosts on the local network or hosts that are authorized clients of this server. Use either a packet filter at the system level (local packet filter) or a centralized packet filter on the firewall. Note, however, that using a firewall in front of your network will not secure the service itself, but will limit the risk to internal attacks.”

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases





NFS Security and Delphix

This finding is ultimately expected depending on configuration, and may not be a concern.

The Delphix Continuous Data Engine leverages NFS (v3 or v4) filesystem shares for Virtualization activities on Linux or Unix hosts, including virtual database provisioning and data ingestion (depending on the database or appdata platform).  

Filesystems shared from Delphix are secured with an IP address restriction; share permissions are limited to only the intended host, based on one of two values:

1. IP address used in the Environment configuration for discovery. If hostname or FQDN is used, the Engine will resolve the IP address and use this for access restriction.

2. NFS Addresses configured for the Environment. This is an optional configuration parameter for all Linux / Unix hosts to allow access to multiple IP addresses from a given host. This feature may be leveraged for those hosts with multiple network interfaces that can reach the Delphix Engine.

These NFS filesystems are mounted and shared dynamically based on the Dataset state; if a given Dataset is disabled, the NFS shares are removed.

Beyond this, there is one additional NFS share /public, which is used in our automation for Environment Validation. During a Dataset provision operation, the Engine will execute a test mount of this /public share temporarily to ensure the OS user configured has the proper permissions to mount NFS filesystems before attempting to actually provision the Dataset.  

This /public NFS filesystem is read-only, and empty, but is not IP address restricted.

/public NFS filesystem is always available/shared in versions up to and including  In and later, /public is only exposed during Environment Validation.

Qualys QID 66002 also expresses a possible concern in the exposure of NFSv3 mounts, visible (not necessarily accessible) from a remote host, and that may be perceived as a vulnerability.  If this is a specific function of concern, the DevOps Data Platform NFSv4 feature should be leveraged.  


Beginning in 7.0, if no NFSv3 mounts are active from the Continuous Data Engine, NFSv3 services will be stopped on the engine, and showmount requests will not return any result, thereby removing the finding from the security scanner.



Delphix Continuous Data Engine no longer exports /public without IP restrictions. Please see How to Test NFS Mounting from Target Hosts (KBA5873) for further details


Delphix does not leverage the /etc/exports function offered in many Linux / Unix NFS platforms; the share permissions are handled dynamically.

Beyond the solutions mentioned here and changes in the Continuous Data Engine, Network Security teams have other options available as mentioned in the Qualys report, to apply a firewall or packet filtering, though these can introduce latency.

In Delphix version and later, an additional option is offered which explicitly disables all NFSv3 services on a Continuous Data Engine.  However, this should be used with caution; if the Engine is using NFSv3 for any hosts where NFSv4 is unavailable due to missing requirements, the VDBs provisioned to those hosts will be unavailable.

The following documentation links provide details on enabilng NFSv4 and explicit disable of NFSv3 (via NFSv4 only setting).