|
MySQL Create Database Bypass and Privilege Escalation
|
|
Secunia Advisory:
|
SA21506
|
|
|
Release Date:
|
2006-08-17
|
|
Last Update:
|
2006-10-05
|
|
Popularity:
|
16,074 views
|
|
|
Critical:
|
Not critical
|
|
Impact:
|
Security Bypass
Privilege escalation
|
|
Where:
|
From local network
|
|
Solution Status:
|
Vendor Workaround
|
|
| Software: | MySQL 5.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Two vulnerabilities have been reported in MySQL, which can be exploited by malicious users to bypass certain security restrictions and perform certain actions with escalated privileges.
1) A user, who has been granted access to a certain database but not privileges to create additional databases, can create a database where the name differs only by the case of one or more letters from the database which the user has access to.
Successful exploitation requires that MySQL runs on a system with a file system supporting case-sensitive file names.
2) An error caused due to arguments to suid routines being calculated in an incorrect security context can be exploited to execute arbitrary DML statements with the privileges of the routine's definer via a stored routine.
Successful exploitation requires that the user has "EXECUTE" privileges on the stored routine.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
