Bug #46220 | User cannot fully SHOW CREATE PROCEDURE | ||
---|---|---|---|
Submitted: | 16 Jul 2009 13:38 | Modified: | 16 Jul 2009 13:51 |
Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S2 (Serious) |
Version: | 5.1.35, 5.1.36, 5.0.83 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[16 Jul 2009 13:38]
Peter Laursen
[16 Jul 2009 13:50]
Valeriy Kravchuk
I think our manual clearly explains what privileges are required. Please, read http://dev.mysql.com/doc/refman/5.1/en/show-create-procedure.html: "Both statements require that you be the owner of the routine or have SELECT access to the mysql.proc table. If you do not have privileges for the routine itself, the value displayed for the Create Procedure or Create Function field will be NULL." This is how it works by design, so - not a bug. Please, check.
[16 Jul 2009 13:50]
Peter Laursen
oops .. http://dev.mysql.com/doc/refman/5.0/en/show-create-procedure.html "Both statements require that you be the owner of the routine or have SELECT access to the mysql.proc table. If you do not have privileges for the routine itself, the value displayed for the Create Procedure or Create Function field will be NULL." .. so not a bug (if documentation is specification). I still do not like this!
[16 Jul 2009 13:51]
Peter Laursen
who came first? :-)
[22 Feb 2016 16:38]
Yael Goldberg
This is a bug as the solution is a security hole. The only solution requires granting access to ALL procedures (in mysql.proc), even those that are associated to a database that the user does not have access to. It should be made possible to give users access to procedures only in specific databases.