CVE-2003-0150: Critical severity ORACLE MySQL vulnerability

Published Mar 21, 2003
·
Updated

MySQL 3.23.55 and earlier creates world-writeable files and allows mysql users to gain root privileges by using the "SELECT INFO OUTFILE" operator to overwrite a configuration file and cause mysql to run as root upon restart, as demonstrated by modifying my.cnf.

Affected Software

6 affected components
ORACLE MySQL=3.23.52
ORACLE MySQL=3.23.53
ORACLE MySQL=3.23.53a
ORACLE MySQL=3.23.54
ORACLE MySQL=3.23.54a
ORACLE MySQL=3.23.55

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Ensure the MySQL configuration file (my.cnf) is not world-writable and is owned by root. Example: chown root:root /path/to/my.cnf; chmod 644 /path/to/my.cnf (remove 'others' write permission).

    my.cnf (MySQL configuration file) file_permissions = remove world-writable (no 'others' write); owned by root
  2. Configuration

    Remove the FILE privilege from any database accounts that do not explicitly require it to prevent writing files via SELECT ... INTO OUTFILE. Example: REVOKE FILE ON *.* FROM 'username'@'host'; FLUSH PRIVILEGES;

    MySQL server FILE privilege = revoke from non-administrative accounts
  3. Compensating control

    Restrict who can modify MySQL configuration and restart the server. Limit access to service management (for example, systemctl/service control) and to directories containing MySQL config/data so unprivileged mysql users cannot overwrite configuration and trigger a restart that runs the server as root.

  4. Operational

    Audit my.cnf and other MySQL configuration files for unauthorized modifications, compare to known-good backups, and restore any altered files. If unauthorized changes are found, perform a host compromise investigation and remediate (contain, eradicate) before allowing service restart.

Event History

Mar 21, 2003
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Mar 24, 2003
Data Sourced
via NVD·05:00 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2003-0150?

CVE-2003-0150 is considered a critical vulnerability due to its potential to allow unprivileged MySQL users to gain root privileges.

2

How do I fix CVE-2003-0150?

To fix CVE-2003-0150, upgrade your MySQL installation to version 3.23.56 or later, which addresses this vulnerability.

3

What are the affected versions for CVE-2003-0150?

CVE-2003-0150 affects MySQL versions 3.23.55 and earlier.

4

How does CVE-2003-0150 exploit the system?

CVE-2003-0150 allows attackers to use the 'SELECT * INFO OUTFILE' operator to overwrite MySQL's configuration file, enabling execution as root.

5

Can CVE-2003-0150 be mitigated without an upgrade?

Mitigating CVE-2003-0150 without an upgrade may involve altering file permissions to prevent world-writable files, but complete resolution requires upgrading.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203