Bug #7214 information_schema: unauthorized user can see metadata

Description:
If a user has no privileges at all for an object, the user 
should be unable to see the information_schema row that 
describes the object. But a user with no privileges on any 
routine can see information_schema.routines rows, and 
a user with a privilege on only one column can see all 
columns in information_schema.columns. 
 
I am aware that "describe table_name" would show all columns 
anyway. 
 

How to repeat:
/* As user 'root', set up table and grant select privilege on one column to user 'piotr' */ 
 
mysql> create table tb (s1 int, s2 int, s3 int) engine=memory; 
Query OK, 0 rows affected (0.01 sec) 
 
mysql> grant select on tb (s2) to piotr; 
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that 
corresponds to your MySQL server version for the right syntax to use near '(s2) to piotr' at 
line 1 
mysql> grant select (s2) on tb to piotr; 
Query OK, 0 rows affected (0.00 sec) 
 
/* now switch to being user 'piotr' and select the columns in table. all are visible. */ 
/* (I have assumed that the database is 'db5'. Replace with whatever database contains table 
tb.) */ 
 
mysql> select current_user; 
+--------------+ 
| current_user | 
+--------------+ 
| piotr@%      | 
+--------------+ 
1 row in set (0.00 sec) 
 
mysql> select s2 from db5.tb; 
Empty set (0.00 sec) 
 
mysql> select s1, s3 from db5.tb; 
ERROR 1143 (42000): SELECT command denied to user 'piotr'@'localhost' for column 's1' in 
table 'tb' 
mysql> select table_name, column_name from information_schema.columns 
    -> where table_schema = 'db5' and table_name = 'tb'; 
+------------+-------------+ 
| table_name | column_name | 
+------------+-------------+ 
| tb         | s1          | 
| tb         | s2          | 
| tb         | s3          | 
+------------+-------------+ 
3 rows in set (0.00 sec)

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/internals/23556

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/internals/23612

Ok to push

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/internals/23657

Fixed in 5.0.4

Fixed in 5.0.4

Noted in 5.0.4 changelog.