CVE-2006-4226
Last modified
CVE-2006-4226 is a vulnerability of currently unknown severity. MySQL before 4.1.21, 5.0 before 5.0.25, and 5.1 before 5.1.12, when run on case-sensitive filesystems, allows remote authenticated users to create or access a database when the database name differs only in case from a database for which they have permissions.. EPSS estimates a 2.73% chance of exploitation in the next 30 days.
Description
MySQL before 4.1.21, 5.0 before 5.0.25, and 5.1 before 5.1.12, when run on case-sensitive filesystems, allows remote authenticated users to create or access a database when the database name differs only in case from a database for which they have permissions.
Metrics
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Mysql | Mysql | 4.1.0 | — |
| Mysql | Mysql | 4.1.2 | — |
| Mysql | Mysql | 4.1.3 | — |
| Mysql | Mysql | 4.1.8 | — |
| Mysql | Mysql | 4.1.10 | — |
| Mysql | Mysql | 4.1.12 | — |
| Mysql | Mysql | 4.1.13 | — |
| Mysql | Mysql | 4.1.14 | — |
| Mysql | Mysql | 4.1.15 | — |
| 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.1.5 | — |
| Oracle | Mysql | 4.0.0 | — |
| Oracle | Mysql | 4.0.1 | — |
| Oracle | Mysql | 4.0.2 | — |
| Oracle | Mysql | 4.0.3 | — |
| Oracle | Mysql | 4.0.4 | — |
| Oracle | Mysql | 4.0.5 | — |
| Oracle | Mysql | 4.0.5a | — |
| Oracle | Mysql | 4.0.6 | — |
| Oracle | Mysql | 4.0.7 | — |
| Oracle | Mysql | 4.0.8 | — |
| Oracle | Mysql | 4.0.9 | — |
| Oracle | Mysql | 4.0.10 | — |
| Oracle | Mysql | 4.0.11 | — |
| Oracle | Mysql | 4.0.12 | — |
| Oracle | Mysql | 4.0.13 | — |
| Oracle | Mysql | 4.0.14 | — |
| Oracle | Mysql | 4.0.15 | — |
| Oracle | Mysql | 4.0.16 | — |
| Oracle | Mysql | 4.0.17 | — |
| Oracle | Mysql | 4.0.18 | — |
| Oracle | Mysql | 4.0.19 | — |
| Oracle | Mysql | 4.0.20 | — |
| Oracle | Mysql | 4.0.21 | — |
| Oracle | Mysql | 4.0.23 | — |
| Oracle | Mysql | 4.0.24 | — |
| Oracle | Mysql | 4.0.25 | — |
| Oracle | Mysql | 4.0.26 | — |
Showing 50 of 91 affected configurations. See NVD for the full list.
References
- http://bugs.mysql.com/bug.php?id=17647Exploit, Patch
- http://secunia.com/advisories/21506Exploit, Patch, Vendor Advisory
- http://www.securityfocus.com/bid/19559Exploit, Patch
- http://www.us-cert.gov/cas/techalerts/TA07-072A.htmlUS Government Resource
- http://bugs.mysql.com/bug.php?id=17647Exploit, Patch
- http://secunia.com/advisories/21506Exploit, Patch, Vendor Advisory
- http://www.securityfocus.com/bid/19559Exploit, Patch
- http://www.us-cert.gov/cas/techalerts/TA07-072A.htmlUS Government Resource
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2006-4226?
How severe is CVE-2006-4226?
How do I fix CVE-2006-4226?
Are you affected by CVE-2006-4226?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST