LOAD DATA statement can load a
file located on the server host, or, if the
LOCAL keyword is specified, on the client host.
There are two potential security issues with the
LOCAL version of
The transfer of the file from the client host to the server host is initiated by the MySQL server. In theory, a patched server could be built that would tell the client program to transfer a file of the server's choosing rather than the file named by the client in the
LOAD DATAstatement. Such a server could access any file on the client host to which the client user has read access. (A patched server could in fact reply with a file-transfer request to any statement, not just
LOAD DATA LOCAL, so a more fundamental issue is that clients should not connect to untrusted servers.)
In a Web environment where the clients are connecting from a Web server, a user could use
LOAD DATA LOCALto read any files that the Web server process has read access to (assuming that a user could run any statement against the SQL server). In this environment, the client with respect to the MySQL server actually is the Web server, not a remote program being run by users who connect to the Web server.
LOAD DATA issues, clients
should avoid using
LOCAL. To avoid connecting
to untrusted servers, clients can establish a secure connection
and verify the server identity by connecting using the
and the appropriate CA certificate.
To enable adminstrators and applications to manage the local data
LOCAL configuration works
On the server side:
local_infilesystem variable controls server-side
LOCALcapability. Depending on the
local_infilesetting, the server refuses or permits local data loading by clients that have
LOCALenabled on the client side. By default,
To explicitly cause the server to refuse or permit
LOAD DATA LOCALstatements (regardless of how client programs and libraries are configured at build time or runtime), start mysqld with
local_infiledisabled or enabled, respectively.
local_infilecan also be set at runtime.
On the client side:
ENABLED_LOCAL_INFILECMake option controls the compiled-in default
LOCALcapability for the MySQL client library. Clients that make no explicit arrangements therefore have
LOCALcapability disabled or enabled according to the
ENABLED_LOCAL_INFILEsetting specified at MySQL build time.
By default, the client library in MySQL binary distributions is compiled with
ENABLED_LOCAL_INFILEdisabled. If you compile MySQL from source, configure it with
ENABLED_LOCAL_INFILEdisabled or enabled based on whether clients that make no explicit arrangements should have
LOCALcapability disabled or enabled, respectively.
Client programs that use the C API can control load data loading explicitly by invoking
mysql_options()to disable or enable the
MYSQL_OPT_LOCAL_INFILEoption. See Section 188.8.131.52, “mysql_options()”.
If you use
LOAD DATA LOCALin Perl scripts or other programs that read the
[client]group from option files, you can add an
local-infileoption setting to that group. To prevent problems for programs that do not understand this option, specify it using the
In all cases, successful use of a
LOCALload operation by a client also requires that the server permits it.
LOCAL capability is disabled, on either the
server or client side, a client that attempts to issue a
LOCAL statement receives the following error message:
ERROR 3950 (42000): Loading local data is disabled; this must be enabled on both the client and server side