Bug #27515 DROP previlege is not required anymore for RENAME TABLE
| Submitted: | 29 Mar 2007 10:15 | Modified: | 27 Apr 2007 4:25 |
|---|---|---|---|
| Reporter: | Victoria Reznichenko | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Security: Privileges | Severity: | S2 (Serious) |
| Version: | 4.1, 5.0, 5.1 | OS: | Any (any) |
| Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
| Tags: | bfsm_2007_04_05, regression | ||
[29 Mar 2007 10:15]
Victoria Reznichenko
[17 Apr 2007 11:52]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/24642 ChangeSet@1.2644, 2007-04-17 16:52:50+05:00, ramil@mysql.com +3 -0 Fix for bug #27515: DROP previlege is not required anymore for RENAME TABLE Added missed DROP privilege check on the original table for RENAME TABLE command.
[26 Apr 2007 11:32]
Bugs System
Pushed into 4.1.23
[26 Apr 2007 11:37]
Bugs System
Pushed into 5.0.42
[26 Apr 2007 11:38]
Bugs System
Pushed into 5.1.18-beta
[27 Apr 2007 4:25]
Paul DuBois
Noted in 4.1.23, 5.0.42, 5.1.18 changelogs. Security fix: The requirement of the DROP privilege for RENAME TABLE was not being enforced.
[9 May 2007 3:20]
Guangbao Ni
merge into mysql-4.1-ndb tree
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.046 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.