The MySQL PolyFromWKB() function did not sanity check Well-Known Binary (WKB) data, which could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3840)

A flaw in the way MySQL processed certain JOIN queries could allow a remote, authenticated attacker to cause excessive CPU use (up to 100%), if a stored procedure contained JOIN queries, and that procedure was executed twice in sequence. (CVE-2010-3839)

A flaw in the way MySQL processed queries that provide a mixture of numeric and longblob data types to the LEAST or GREATEST function, could allow a remote, authenticated attacker to crash mysqld.
(CVE-2010-3838)

A flaw in the way MySQL processed PREPARE statements containing both GROUP_CONCAT and the WITH ROLLUP modifier could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3837)

MySQL did not properly pre-evaluate LIKE arguments in view prepare mode, possibly allowing a remote, authenticated attacker to crash mysqld. (CVE-2010-3836)

A flaw in the way MySQL processed statements that assign a value to a user-defined variable and that also contain a logical value evaluation could allow a remote, authenticated attacker to crash mysqld.
(CVE-2010-3835)

A flaw in the way MySQL evaluated the arguments of extreme-value functions, such as LEAST and GREATEST, could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3833)

A flaw in the way MySQL handled LOAD DATA INFILE requests allowed MySQL to send OK packets even when there were errors. (CVE-2010-3683)

A flaw in the way MySQL processed EXPLAIN statements for some complex SELECT queries could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3682)

A flaw in the way MySQL processed certain alternating READ requests provided by HANDLER statements could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3681)

A flaw in the way MySQL processed CREATE TEMPORARY TABLE statements that define NULL columns when using the InnoDB storage engine, could allow a remote, authenticated attacker to crash mysqld.
(CVE-2010-3680)

A flaw in the way MySQL processed certain values provided to the BINLOG statement caused MySQL to read unassigned memory. A remote, authenticated attacker could possibly use this flaw to crash mysqld.
(CVE-2010-3679)

A flaw in the way MySQL processed SQL queries containing IN or CASE statements, when a NULL argument was provided as one of the arguments to the query, could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3678)

A flaw in the way MySQL processed JOIN queries that attempt to retrieve data from a unique SET column could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3677)

Note: CVE-2010-3840, CVE-2010-3838, CVE-2010-3837, CVE-2010-3835, CVE-2010-3833, CVE-2010-3682, CVE-2010-3681, CVE-2010-3680, CVE-2010-3678, and CVE-2010-3677 only cause a temporary denial of service, as mysqld was automatically restarted after each crash.

These updated packages upgrade MySQL to version 5.1.52. Refer to the MySQL release notes for a full list of changes :

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html

After installing this update, the MySQL server daemon (mysqld) will be restarted automatically.

The remote host is running a version of Mac OS X 10.5 that does not have Security Update 2011-004 applied. This update contains security- related fixes for the following components :

  - AirPort
  - App Store
  - ColorSync
  - CoreGraphics
  - ImageIO
  - Libsystem
  - libxslt
  - MySQL
  - patch
  - Samba
  - servermgrd
  - subversion

This update fixes the following security issue :

  - 676974: mysql-cluster: security issues fixed in MySQL     5.1.51

This update also fixes the following non-security issue :

  - 635645: mysql init script fails to start when SELinux is     enabled

Multiple vulnerabilities were discovered and corrected in mysql :

  - During evaluation of arguments to extreme-value     functions (such as LEAST() and GREATEST()), type errors     did not propagate properly, causing the server to crash     (CVE-2010-3833).

  - The server could crash after materializing a derived     table that required a temporary table for grouping     (CVE-2010-3834).

  - A user-variable assignment expression that is evaluated     in a logical expression context can be precalculated in     a temporary table for GROUP BY. However, when the     expression value is used after creation of the temporary     table, it was re-evaluated, not read from the table and     a server crash resulted (CVE-2010-3835).

  - Pre-evaluation of LIKE predicates during view     preparation could cause a server crash (CVE-2010-3836).

  - GROUP_CONCAT() and WITH ROLLUP together could cause a     server crash (CVE-2010-3837).

  - Queries could cause a server crash if the GREATEST() or     LEAST() function had a mixed list of numeric and     LONGBLOB arguments, and the result of such a function     was processed using an intermediate temporary table     (CVE-2010-3838).

  - Queries with nested joins could cause an infinite loop     in the server when used from stored procedures and     prepared statements (CVE-2010-3839).

  - The PolyFromWKB() function could crash the server when     improper WKB data was passed to the function     (CVE-2010-3840).

The updated packages have been patched to correct these issues.

ID	名稱	產品	系列	已發布	已更新	嚴重性
60940	Scientific Linux Security Update : mysql on SL6.x i386/x86_64	Nessus	Scientific Linux Local Security Checks	2012/8/1	2021/1/14	medium
55415	Mac OS X Multiple Vulnerabilities (Security Update 2011-004)	Nessus	MacOS X Local Security Checks	2011/6/24	2024/5/28	high
75590	openSUSE Security Update : libmysqlclusterclient16 (openSUSE-SU-2011:0774-1)	Nessus	SuSE Local Security Checks	2014/6/13	2021/1/14	medium
50534	Mandriva Linux Security Advisory : mysql (MDVSA-2010:223)	Nessus	Mandriva Local Security Checks	2010/11/10	2021/1/6	medium

偵測

搜尋 Plugin

medium

high

medium

medium