Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
12.1.1
-
None
-
Not for Release Notes
Description
Hello, I found that the server crashes when CREATE ROLE is executed after the mysql.procs_priv table has been modified.
Even though changing a system table isn't a standard operation, it would be much safer if the server returned an error about the table's invalid state instead of crashing. This would make the server more resilient to unexpected configurations.
How to repeat
ALTER TABLE mysql.servers DROP COLUMN Owner; |
INSERT INTO mysql.servers VALUES (0,0,0,0,0,0,0,0); |
FLUSH PRIVILEGES ; |
ALTER TABLE mysql.plugin DROP COLUMN dl; |
INSTALL SONAME "ha_example" ; |
CREATE OR REPLACE TABLE mysql.procs_priv (id INT ); |
INSERT INTO mysql.procs_priv VALUES (0); |
CREATE ROLE r; |
Attachments
Issue Links
- duplicates
-
MDEV-28482 SIGSEGV in get_access_value_from_val_int
-
- Closed
-
- relates to
-
MDEV-24193 UBSAN: sql/sql_acl.cc:9985:29: runtime error: member access within null pointer of type 'struct TABLE' , ASAN: use-after-poison in handle_grant_table
-
- Closed
-
-
MDEV-35622 SEGV, ASAN use-after-poison when reading system table with less than expected number of columns
-
- Closed
-