Login or Register to Ask a Question and Join Our Community


Security Advisories (RSS)

Mandriva: mysql

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) Mandriva: mysql
# 1  
Old 01-17-2010
Mandriva: mysql
LinuxSecurity.com: Multiple vulnerabilities has been found and corrected in mysql:mysqld in MySQL 5.0.x before 5.0.88 and 5.1.x before 5.1.41 doesnot (1) properly handle errors during execution of certain SELECTstatements with subqueries, and does not (2) preserve certainnull_value flags during execution of statements that use theGeomFromWKB function, which allows remote authenticated users tocause a denial of service (daemon crash) via a crafted statement(CVE-2009-4019).The vio_verify_callback function in viosslfactories.c in MySQL5.0.x before 5.0.88 and 5.1.x before 5.1.41, when OpenSSL is used,accepts a value of zero for the depth of X.509 certificates, whichallows man-in-the-middle attackers to spoof arbitrary SSL-based MySQLservers via a crafted certificate, as demonstrated by a certificatepresented by a server linked against the yaSSL library (CVE-2009-4028).MySQL 5.1.x before 5.1.41 allows local users to bypass certainprivilege checks by calling CREATE TABLE on a MyISAM table withmodified (1) DATA DIRECTORY or (2) INDEX DIRECTORY argumentsthat are originally associated with pathnames without symlinks,and that can point to tables created at a future time at which apathname is modified to contain a symlink to a subdirectory of theMySQL data home directory, related to incorrect calculation of themysql_unpacked_real_data_home value. NOTE: this vulnerability existsbecause of an incomplete fix for CVE-2008-4098 and CVE-2008-2079(CVE-2009-4030).The updated packages have been patched to correct theseissues. Additionally for 2009.1 and 2010.0 mysql has also been upgradedto the latest stable 5.1 release (5.1.42).

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT CENTOS

cgi::session::driver::mysql

CGI::Session::Driver::mysql(3)				User Contributed Perl Documentation			    CGI::Session::Driver::mysql(3)

NAME

       CGI::Session::Driver::mysql - CGI::Session driver for MySQL database

SYNOPSIS

	   $s = new CGI::Session( 'driver:mysql', $sid);
	   $s = new CGI::Session( 'driver:mysql', $sid, { DataSource  => 'dbi:mysql:test',
							  User	      => 'sherzodr',
							  Password    => 'hello' });
	   $s = new CGI::Session( 'driver:mysql', $sid, { Handle => $dbh } );

DESCRIPTION

       mysql stores session records in a MySQL table. For details see CGI::Session::Driver::DBI, its parent class.

       It's especially important for the MySQL driver that the session ID column be defined as a primary key, or at least "unique", like this:

	CREATE TABLE sessions (
	    id CHAR(32) NOT NULL PRIMARY KEY,
	    a_session TEXT NOT NULL
	 );

       To use different column names, change the 'create table' statement, and then simply do this:

	   $s = new CGI::Session('driver:mysql', undef,
	   {
	       TableName=>'session',
	       IdColName=>'my_id',
	       DataColName=>'my_data',
	       DataSource=>'dbi:mysql:project',
	   });

       or

	   $s = new CGI::Session('driver:mysql', undef,
	   {
	       TableName=>'session',
	       IdColName=>'my_id',
	       DataColName=>'my_data',
	       Handle=>$dbh,
	   });

   DRIVER ARGUMENTS
       mysql driver supports all the arguments documented in CGI::Session::Driver::DBI. In addition, DataSource argument can optionally leave
       leading "dbi:mysql:" string out:

	   $s = new CGI::Session( 'driver:mysql', $sid, {DataSource=>'shopping_cart'});
	   # is the same as:
	   $s = new CGI::Session( 'driver:mysql', $sid, {DataSource=>'dbi:mysql:shopping_cart'});

   BACKWARDS COMPATIBILITY
       As of V 4.30, the global variable $CGI::Session::MySQL::TABLE_NAME cannot be used to set the session table's name.

       This is due to changes in CGI::Session::Driver's new() method, which now allows the table's name to be changed (as well as allowing both
       the 'id' column name and the 'a_session' column name to be changed).

       See the documentation for CGI::Session::Driver::DBI for details.

       In particular, the new syntax for "new()" applies to all database drivers, whereas the old - and bad - global variable method only applied
       to MySQL.

       Alternately, call $session -> table_name('new_name') just after creating the session object if you wish to change the session table's name.

LICENSING

       For support and licensing see CGI::Session.

perl v5.16.3							    2008-07-16					    CGI::Session::Driver::mysql(3)