CVE-2006-4031
Last modified
CVE-2006-4031 is a vulnerability of currently unknown severity. MySQL 4.1 before 4.1.21 and 5.0 before 5.0.24 allows a local user to access a table through a previously created MERGE table, even after the user's privileges are revoked for the original table, which might violate intended security policy.. EPSS estimates a 1.74% chance of exploitation in the next 30 days.
Description
MySQL 4.1 before 4.1.21 and 5.0 before 5.0.24 allows a local user to access a table through a previously created MERGE table, even after the user's privileges are revoked for the original table, which might violate intended security policy.
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.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 | — |
| Oracle | Mysql | 3.22.27 | — |
| Oracle | Mysql | 3.22.28 | — |
| Oracle | Mysql | 3.22.29 | — |
| Oracle | Mysql | 3.22.30 | — |
| Oracle | Mysql | 3.22.32 | — |
| Oracle | Mysql | 3.23 | — |
| Oracle | Mysql | 3.23.0 | Alpha |
| Oracle | Mysql | 3.23.1 | — |
| Oracle | Mysql | 3.23.2 | — |
| Oracle | Mysql | 3.23.3 | — |
| Oracle | Mysql | 3.23.4 | — |
| Oracle | Mysql | 3.23.5 | — |
| Oracle | Mysql | 3.23.6 | — |
| Oracle | Mysql | 3.23.7 | — |
| Oracle | Mysql | 3.23.8 | — |
| Oracle | Mysql | 3.23.9 | — |
| Oracle | Mysql | 3.23.10 | — |
| Oracle | Mysql | 3.23.11 | — |
| Oracle | Mysql | 3.23.12 | — |
| Oracle | Mysql | 3.23.13 | — |
| Oracle | Mysql | 3.23.14 | — |
| Oracle | Mysql | 3.23.15 | — |
| Oracle | Mysql | 3.23.16 | — |
| Oracle | Mysql | 3.23.17 | — |
| Oracle | Mysql | 3.23.18 | — |
| Oracle | Mysql | 3.23.19 | — |
| Oracle | Mysql | 3.23.20 | Beta |
| Oracle | Mysql | 3.23.21 | — |
| Oracle | Mysql | 3.23.22 | — |
Showing 50 of 146 affected configurations. See NVD for the full list.
References
- http://bugs.mysql.com/bug.php?id=15195Exploit, Patch
- http://secunia.com/advisories/21259Patch, Vendor Advisory
- http://www.us-cert.gov/cas/techalerts/TA07-072A.htmlUS Government Resource
- http://bugs.mysql.com/bug.php?id=15195Exploit, Patch
- http://secunia.com/advisories/21259Patch, Vendor Advisory
- 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-4031?
How severe is CVE-2006-4031?
How do I fix CVE-2006-4031?
Are you affected by CVE-2006-4031?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
