CVE-2008-7247
Last modified
CVE-2008-7247 is a vulnerability of currently unknown severity. sql/sql_table.cc in MySQL 5.0.x through 5.0.88, 5.1.x through 5.1.41, and 6.0 before 6.0.9-alpha, when the data home directory contains a symlink to a different filesystem, allows remote authenticated users to bypass intended access restrictions by calling CREATE TABLE with a (1) DATA DIRECTORY or (2) INDEX DIRECTORY argument referring to a subdirectory that requires following this symlink.. EPSS estimates a 1.77% chance of exploitation in the next 30 days.
Description
sql/sql_table.cc in MySQL 5.0.x through 5.0.88, 5.1.x through 5.1.41, and 6.0 before 6.0.9-alpha, when the data home directory contains a symlink to a different filesystem, allows remote authenticated users to bypass intended access restrictions by calling CREATE TABLE with a (1) DATA DIRECTORY or (2) INDEX DIRECTORY argument referring to a subdirectory that requires following this symlink.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Mysql | Mysql | 5.0.0 | — |
| Mysql | Mysql | 5.0.1 | — |
| Mysql | Mysql | 5.0.2 | — |
| Mysql | Mysql | 5.0.3 | — |
| Mysql | Mysql | 5.0.4 | — |
| Mysql | Mysql | 5.0.5 | — |
| Mysql | Mysql | 5.0.5.0.21 | — |
| Mysql | Mysql | 5.0.10 | — |
| Mysql | Mysql | 5.0.15 | — |
| Mysql | Mysql | 5.0.16 | — |
| Mysql | Mysql | 5.0.17 | — |
| Mysql | Mysql | 5.0.20 | — |
| Mysql | Mysql | 5.0.22.1.0.1 | — |
| Mysql | Mysql | 5.0.24 | — |
| Mysql | Mysql | 5.0.30 | — |
| Mysql | Mysql | 5.0.36 | — |
| Mysql | Mysql | 5.0.44 | — |
| Mysql | Mysql | 5.0.54 | — |
| Mysql | Mysql | 5.0.56 | — |
| Mysql | Mysql | 5.0.60 | — |
| Mysql | Mysql | 5.0.66 | — |
| Mysql | Mysql | 5.0.82 | — |
| Mysql | Mysql | 5.1.5 | — |
| Mysql | Mysql | 5.1.23 | — |
| Mysql | Mysql | 5.1.32 | — |
| Mysql | Mysql | 6.0.9 | — |
| Oracle | Mysql | 5.0.0 | Alpha |
| Oracle | Mysql | 5.0.3 | Beta |
| Oracle | Mysql | 5.0.6 | — |
| Oracle | Mysql | 5.0.7 | — |
| Oracle | Mysql | 5.0.8 | — |
| Oracle | Mysql | 5.0.11 | — |
| Oracle | Mysql | 5.0.12 | — |
| Oracle | Mysql | 5.0.13 | — |
| Oracle | Mysql | 5.0.14 | — |
| Oracle | Mysql | 5.0.18 | — |
| Oracle | Mysql | 5.0.19 | — |
| Oracle | Mysql | 5.0.21 | — |
| Oracle | Mysql | 5.0.22 | — |
| Oracle | Mysql | 5.0.23 | — |
| Oracle | Mysql | 5.0.25 | — |
| Oracle | Mysql | 5.0.26 | — |
| Oracle | Mysql | 5.0.27 | — |
| Oracle | Mysql | 5.0.30 | Sp1 |
| Oracle | Mysql | 5.0.32 | — |
| Oracle | Mysql | 5.0.33 | — |
| Oracle | Mysql | 5.0.37 | — |
| Oracle | Mysql | 5.0.38 | — |
| Oracle | Mysql | 5.0.41 | — |
| Oracle | Mysql | 5.0.42 | — |
Showing 50 of 86 affected configurations. See NVD for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2008-7247?
How severe is CVE-2008-7247?
How do I fix CVE-2008-7247?
Are you affected by CVE-2008-7247?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
