CVE-2008-2079: Medium severity mysql vulnerability

Published Mar 13, 2008
·
Updated

MySQL 4.1.24, 5.0.60, 5.1.24, and 6.0.5 fixes an issue allowing an authenticated attacker to gain privileges to tables that will be created by some other database user in future using MyISAM storage engine, if an attacker can predict names of such tables.

Attacker can create a table using DATA/INDEX DIRECTORY directives causing data and index files (.MYD/.MYI) to be created in some other directory writable by mysql server, including directories used to store table files of other users' databases. If victim later creates table with the same name, attacker's data and index files are overwritten by victim's files, but access privileges are not revoked. Attacker gains access to newly created victim's table.

References: http://bugs.mysql.com/bug.php?id=32167 http://dev.mysql.com/doc/refman/4.1/en/news-4-1-24.html http://dev.mysql.com/doc/refman/5.0/en/releasenotes-es-5-0-60.html http://dev.mysql.com/doc/refman/5.1/en/news-5-1-24.html http://dev.mysql.com/doc/refman/6.0/en/news-6-0-5.html

Other sources

MySQL 4.1.x before 4.1.24, 5.0.x before 5.0.60, 5.1.x before 5.1.24, and 6.0.x before 6.0.5 allows local users to bypass certain privilege checks by calling CREATE TABLE on a MyISAM table with modified (1) DATA DIRECTORY or (2) INDEX DIRECTORY arguments that are within the MySQL home data directory, which can point to tables that are created in the future.

Red Hat

Affected Software

16 affected componentsFixes available
redhat/mysql<0:4.1.22-2.el4
0:4.1.22-2.el4
redhat/mysql<0:5.0.77-3.el5
0:5.0.77-3.el5
redhat/httpd<0:2.0.63-2.el4
0:2.0.63-2.el4
redhat/mysql<0:5.0.50sp1a-2.el4
0:5.0.50sp1a-2.el4
redhat/mysql-connector-odbc<0:3.51.24r1071-1.el4
0:3.51.24r1071-1.el4
redhat/php<0:5.1.6-3.el4
0:5.1.6-3.el4
redhat/postgresqlclient7<0:7.4.19-1.el4
0:7.4.19-1.el4
redhat/postgresql-jdbc<0:8.1.412-1jpp.el4
0:8.1.412-1jpp.el4
MySQL mysql>=4.1.0<4.1.24
MySQL mysql>=5.0.0<5.0.60
MySQL mysql>=5.1.0<5.1.24
Oracle MySQL>=6.0.0<6.0.5
Debian Debian Linux=4.0
Canonical Ubuntu Linux=6.06
Canonical Ubuntu Linux=7.10
Canonical Ubuntu Linux=8.04

Event History

Mar 13, 2008
CVE Published
via Red Hat·12:00 AM
May 5, 2008
Data Sourced
via Red Hat·03:31 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2008-2079?

CVE-2008-2079 has a moderate severity rating due to the potential for privilege escalation in MySQL.

2

How do I fix CVE-2008-2079?

To fix CVE-2008-2079, upgrade to MySQL versions 4.1.24, 5.0.60, 5.1.24, or 6.0.5 or later.

3

What versions of MySQL are affected by CVE-2008-2079?

CVE-2008-2079 affects MySQL versions 4.1.0 through 4.1.24, 5.0.0 through 5.0.60, 5.1.0 through 5.1.24, and 6.0.0 through 6.0.5.

4

Who is vulnerable to exploitation of CVE-2008-2079?

Authenticated users who can predict the names of future tables are vulnerable to exploitation of CVE-2008-2079.

5

What impact does CVE-2008-2079 have on MySQL databases?

CVE-2008-2079 allows an authenticated attacker to gain privileges to tables created by other users, potentially compromising database security.

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