Multiple Security Vulnerabilities in The "MySQL" Package



Category :Security
Release Phase :Resolved
Product :Solaris 10 Operating System  
Bug Id :6258187  
Date of Resolved Release :11-AUG-2005 


Impact

Multiple security vulnerabilities in the "MySQL" package, an open source database package bundled with Solaris 10 (see mysqld(1)), may result in one or more of the following issues:

1. An unprivileged "MySQL" user may be able to access and potentially modify sensitive information in database tables.

This issue is referenced in the following document:

2. An unprivileged "MySQL" user may be able to disable a "MySQL" server causing a Denial of Service(DoS).

This issue is referenced in the following document:

3. A local unprivileged UNIX user may be able to overwrite or create arbitrary files on the system with the privileges of a user who invokes the mysqlaccess(1) script.

This issue is referenced in the following document:

4. A "MySQL" user with "INSERT" and "DELETE" privileges may be able to execute arbitrary commands with the privileges of the "MySQL" server due to a security vulnerability in the "CREATE FUNCTION" command.

This issue is referenced in the following document:

5. A "MySQL" user with "INSERT" and "DELETE" privileges may be able to execute arbitrary commands with the privileges of the "MySQL" server due to a security vulnerability in the "udf_init" function.

This issue is referenced in the following document:

6. A "MySQL" user with the "CREATE TEMPORARY TABLES" privilege may be able to overwrite or create files on the system with the privileges of the "MySQL" server.

This issue is referenced in the following document:

Note: The "MySQL" server, mysqld(1), runs as an unprivileged user by default.


Contributing Factors

This issue can occur in the following releases:

SPARC Platform

x86 Platform

Note: Solaris 7, 8 and 9 are not impacted by this issue.

In order for a system to be vulnerable to any of the issues mentioned above, with the exception of issue number 3, the "MySQL" server daemon (mysqld(1)) must be running on the system. To determine if the "MySQL" server daemon is running on the system, the following command can be executed:

    $ pgrep -lf mysqld
    107098 /usr/sfw/sbin/mysqld

In order for the third issue described above to occur a user must invoke the mysqlaccess(1) script.


Symptoms

There are no predictable symptoms that would indicate the described issues have been exploited.


Workaround

In order to prevent issue number 3 above from occurring, sites may wish to stop users from executing the mysqlaccess(1) script until patches can be applied to the system.

To disable the mysqlaccess(1) script the following command can be executed as the root (uid 0) user:

    # chmod 000 /usr/sfw/bin/mysqlaccess

 


Resolution

This issue is addressed in the following releases:

SPARC Platform

x86 Platform






Attachments
This solution has no attachment

 
 
Login Required

You must login and have a valid contract to access Sun's Premium content which includes:

  • Sun Alerts
  • Bugs
  • Patches
  • Solutions
  • White Papers
  • Documentation
  • Support Knowledge

Login Required

You must login and have a valid contract to access Sun's contracted features

Access Legend:

(Login to access)   Sun Contracted Content
(Login to access)   Sun Contracted Feature

Please make use of SunSolve Feedback application by selecting the floating [+] to provide feedback about this specific document.

Search

Article Details
Article ID : 201658
Article Type : Sun Alert
Last reviewed : 2005-08-11
Audience : PUBLIC
Keywords :
Provide feedback  (help)
Page Tools
»  Print This Page
»  Email This Article
»  Bookmark This Article