S-091: MySQL Security Update


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-091: MySQL Security Update
# 1  
Old 12-24-2007
S-091: MySQL Security Update

Several flaws were found in a way:1) MySQL handled symbolic links when database tables were created with explicit "DATE" and "INDEX DIRECTORY" options; and2) MySQL's InnoDB engine handled spatial indexes. The risk is LOW. Data destruction - overwrites tables.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Programming

MYSQL - trigger update on record insert or update

Right I have a MYSQL database with table1 with 3 columns, colA, colB and colC. I want to combine the data in the 3 columns into a 4th column names col_comb. Here's the SQL command that works: UPDATE table1 SET `col_comb` = CONCAT( `colA` , ' - ', `colB` , ', ', `colC` ); So now I want this... (5 Replies)
Discussion started by: barrydocks
5 Replies
Login or Register to Ask a Question
NDB_SHOW_TABLES 					       MySQL Database System						   NDB_SHOW_TABLES

NAME
ndb_show_tables - display list of NDB tables SYNOPSIS
ndb_show_tables [options] DESCRIPTION
ndb_show_tables displays a list of all NDB database objects in the cluster. By default, this includes not only both user-created tables and NDB system tables, but NDB-specific indexes, internal triggers, and MySQL Cluster Disk Data objects as well. The following table includes options that are specific to the MySQL Cluster native backup restoration program ndb_show_tables. Additional descriptions follow the table. For options common to most MySQL Cluster programs (including ndb_show_tables), see Options Common to MySQL Cluster Programs(1). Table 17.26. ndb_show_tables Options and Variables: MySQL Cluster NDB 7.2 +--------------------------+--------------------------------------+-------------------------------------+ |Format | Description | Added / Removed | +--------------------------+--------------------------------------+-------------------------------------+ | | Specifies the database in which the | | | --database=string, | table is found | All MySQL 5.5 based releases | | | | | | -d | | | +--------------------------+--------------------------------------+-------------------------------------+ | | Number of times to repeat output | | | --loops=#, | | All MySQL 5.5 based releases | | | | | | -l | | | +--------------------------+--------------------------------------+-------------------------------------+ | | Limit output to objects of this type | | | --type=#, | | All MySQL 5.5 based releases | | | | | | -t | | | +--------------------------+--------------------------------------+-------------------------------------+ | | Do not qualify table names | | | --unqualified, | | All MySQL 5.5 based releases | | | | | | -u | | | +--------------------------+--------------------------------------+-------------------------------------+ | | Return output suitable for MySQL | | | --parsable, | LOAD DATA INFILE statement | All MySQL 5.5 based releases | | | | | | -p | | | +--------------------------+--------------------------------------+-------------------------------------+ | | Show table temporary flag | | | --show-temp-status | | All MySQL 5.5 based releases | +--------------------------+--------------------------------------+-------------------------------------+ Usage ndb_show_tables [-c connect_string] o --database, -d Specifies the name of the database in which the tables are found. o --loops, -l Specifies the number of times the utility should execute. This is 1 when this option is not specified, but if you do use the option, you must supply an integer argument for it. o --parsable, -p Using this option causes the output to be in a format suitable for use with LOAD DATA INFILE. o --show-temp-status If specified, this causes temporary tables to be displayed. o --type, -t Can be used to restrict the output to one type of object, specified by an integer type code as shown here: o 1: System table o 2: User-created table o 3: Unique hash index Any other value causes all NDB database objects to be listed (the default). o --unqualified, -u If specified, this causes unqualified object names to be displayed. Note Only user-created MySQL Cluster tables may be accessed from MySQL; system tables such as SYSTAB_0 are not visible to mysqld. However, you can examine the contents of system tables using NDB API applications such as ndb_select_all (see ndb_select_all(1)). COPYRIGHT
Copyright (C) 1997, 2014, Oracle and/or its affiliates. All rights reserved. This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/. SEE ALSO
For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online at http://dev.mysql.com/doc/. AUTHOR
Oracle Corporation (http://dev.mysql.com/). MySQL 5.5 01/30/2014 NDB_SHOW_TABLES