Home / mailings [RHSA-2010:0825-01] Moderate: mysql security update
Posted on 03 November 2010
RedHat-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=====================================================================
Red Hat Security Advisory
Synopsis: Moderate: mysql security update
Advisory ID: RHSA-2010:0825-01
Product: Red Hat Enterprise Linux
Advisory URL: https://rhn.redhat.com/errata/RHSA-2010-0825.html
Issue date: 2010-11-03
CVE Names: CVE-2010-3677 CVE-2010-3680 CVE-2010-3681
CVE-2010-3682 CVE-2010-3833 CVE-2010-3835
CVE-2010-3836 CVE-2010-3837 CVE-2010-3838
CVE-2010-3839 CVE-2010-3840
=====================================================================
1. Summary:
Updated mysql packages that fix multiple security issues are now available
for Red Hat Enterprise Linux 5.
The Red Hat Security Response Team has rated this update as having moderate
security impact. Common Vulnerability Scoring System (CVSS) base scores,
which give detailed severity ratings, are available for each vulnerability
from the CVE links in the References section.
2. Relevant releases/architectures:
RHEL Desktop Workstation (v. 5 client) - i386, x86_64
Red Hat Enterprise Linux (v. 5 server) - i386, ia64, ppc, s390x, x86_64
Red Hat Enterprise Linux Desktop (v. 5 client) - i386, x86_64
3. Description:
MySQL is a multi-user, multi-threaded SQL database server. It consists of
the MySQL server daemon (mysqld) and many client programs and libraries.
It was found that the MySQL PolyFromWKB() function did not sanity check
Well-Known Binary (WKB) data. A remote, authenticated attacker could use
specially-crafted WKB data to crash mysqld. This issue only caused a
temporary denial of service, as mysqld was automatically restarted after
the crash. (CVE-2010-3840)
A flaw was found in the way MySQL processed certain JOIN queries. If a
stored procedure contained JOIN queries, and that procedure was executed
twice in sequence, it could cause an infinite loop, leading to excessive
CPU use (up to 100%). A remote, authenticated attacker could use this flaw
to cause a denial of service. (CVE-2010-3839)
A flaw was found in the way MySQL processed queries that provide a mixture
of numeric and longblob data types to the LEAST or GREATEST function. A
remote, authenticated attacker could use this flaw to crash mysqld. This
issue only caused a temporary denial of service, as mysqld was
automatically restarted after the crash. (CVE-2010-3838)
A flaw was found in the way MySQL processed PREPARE statements containing
both GROUP_CONCAT and the WITH ROLLUP modifier. A remote, authenticated
attacker could use this flaw to crash mysqld. This issue only caused a
temporary denial of service, as mysqld was automatically restarted after
the crash. (CVE-2010-3837)
It was found that MySQL did not properly pre-evaluate LIKE arguments in
view prepare mode. A remote, authenticated attacker could possibly use this
flaw to crash mysqld. (CVE-2010-3836)
A flaw was found in the way MySQL processed statements that assign a value
to a user-defined variable and that also contain a logical value
evaluation. A remote, authenticated attacker could use this flaw to crash
mysqld. This issue only caused a temporary denial of service, as mysqld was
automatically restarted after the crash. (CVE-2010-3835)
A flaw was found in the way MySQL evaluated the arguments of extreme-value
functions, such as LEAST and GREATEST. A remote, authenticated attacker
could use this flaw to crash mysqld. This issue only caused a temporary
denial of service, as mysqld was automatically restarted after the crash.
(CVE-2010-3833)
A flaw was found in the way MySQL processed EXPLAIN statements for some
complex SELECT queries. A remote, authenticated attacker could use this
flaw to crash mysqld. This issue only caused a temporary denial of service,
as mysqld was automatically restarted after the crash. (CVE-2010-3682)
A flaw was found in the way MySQL processed certain alternating READ
requests provided by HANDLER statements. A remote, authenticated attacker
could use this flaw to provide such requests, causing mysqld to crash. This
issue only caused a temporary denial of service, as mysqld was
automatically restarted after the crash. (CVE-2010-3681)
A flaw was found in the way MySQL processed CREATE TEMPORARY TABLE
statements that define NULL columns when using the InnoDB storage engine. A
remote, authenticated attacker could use this flaw to crash mysqld. This
issue only caused a temporary denial of service, as mysqld was
automatically restarted after the crash. (CVE-2010-3680)
A flaw was found in the way MySQL processed JOIN queries that attempt to
retrieve data from a unique SET column. A remote, authenticated attacker
could use this flaw to crash mysqld. This issue only caused a temporary
denial of service, as mysqld was automatically restarted after the crash.
(CVE-2010-3677)
All MySQL users are advised to upgrade to these updated packages, which
contain backported patches to correct these issues. After installing this
update, the MySQL server daemon (mysqld) will be restarted automatically.
4. Solution:
Before applying this update, make sure all previously-released errata
relevant to your system have been applied.
This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/docs/DOC-11259
5. Bugs fixed (http://bugzilla.redhat.com/):
628040 - CVE-2010-3677 MySQL: Mysqld DoS (crash) by processing joins involving a table with a unique SET column (MySQL BZ#54575)
628192 - CVE-2010-3680 MySQL: mysqld DoS (assertion failure) by using temporary InnoDB engine tables with nullable columns (MySQL bug #54044)
628328 - CVE-2010-3682 MySQL: mysqld DoS (crash) by processing EXPLAIN statements for complex SQL queries (MySQL bug #52711)
628680 - CVE-2010-3681 MySQL: mysqld DoS (assertion failure) by alternate reads from two indexes on a table using the HANDLER interface (MySQL bug #54007)
640751 - CVE-2010-3833 MySQL: CREATE TABLE ... SELECT causes crash when KILL_BAD_DATA is returned (MySQL Bug#55826)
640819 - CVE-2010-3835 MySQL: crash with user variables, assignments, joins... (MySQL Bug #55564)
640845 - CVE-2010-3836 MySQL: pre-evaluating LIKE arguments in view prepare mode causes crash (MySQL Bug#54568)
640856 - CVE-2010-3837 MySQL: crash when group_concat and "with rollup" in prepared statements (MySQL Bug#54476)
640858 - CVE-2010-3838 MySQL: crash with LONGBLOB and union or update with subquery (MySQL Bug#54461)
640861 - CVE-2010-3839 MySQL: server hangs during JOIN query in stored procedures called twice in a row (MySQL Bug#53544)
640865 - CVE-2010-3840 MySQL: crash when loading data into geometry function PolyFromWKB() (MySQL Bug#51875)
6. Package List:
Red Hat Enterprise Linux Desktop (v. 5 client):
Source:
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Client/en/os/SRPMS/mysql-5.0.77-4.el5_5.4.src.rpm
i386:
mysql-5.0.77-4.el5_5.4.i386.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.i386.rpm
x86_64:
mysql-5.0.77-4.el5_5.4.i386.rpm
mysql-5.0.77-4.el5_5.4.x86_64.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.i386.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.x86_64.rpm
RHEL Desktop Workstation (v. 5 client):
Source:
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Client/en/os/SRPMS/mysql-5.0.77-4.el5_5.4.src.rpm
i386:
mysql-bench-5.0.77-4.el5_5.4.i386.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.i386.rpm
mysql-devel-5.0.77-4.el5_5.4.i386.rpm
mysql-server-5.0.77-4.el5_5.4.i386.rpm
mysql-test-5.0.77-4.el5_5.4.i386.rpm
x86_64:
mysql-bench-5.0.77-4.el5_5.4.x86_64.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.i386.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.x86_64.rpm
mysql-devel-5.0.77-4.el5_5.4.i386.rpm
mysql-devel-5.0.77-4.el5_5.4.x86_64.rpm
mysql-server-5.0.77-4.el5_5.4.x86_64.rpm
mysql-test-5.0.77-4.el5_5.4.x86_64.rpm
Red Hat Enterprise Linux (v. 5 server):
Source:
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/mysql-5.0.77-4.el5_5.4.src.rpm
i386:
mysql-5.0.77-4.el5_5.4.i386.rpm
mysql-bench-5.0.77-4.el5_5.4.i386.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.i386.rpm
mysql-devel-5.0.77-4.el5_5.4.i386.rpm
mysql-server-5.0.77-4.el5_5.4.i386.rpm
mysql-test-5.0.77-4.el5_5.4.i386.rpm
ia64:
mysql-5.0.77-4.el5_5.4.i386.rpm
mysql-5.0.77-4.el5_5.4.ia64.rpm
mysql-bench-5.0.77-4.el5_5.4.ia64.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.i386.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.ia64.rpm
mysql-devel-5.0.77-4.el5_5.4.ia64.rpm
mysql-server-5.0.77-4.el5_5.4.ia64.rpm
mysql-test-5.0.77-4.el5_5.4.ia64.rpm
ppc:
mysql-5.0.77-4.el5_5.4.ppc.rpm
mysql-5.0.77-4.el5_5.4.ppc64.rpm
mysql-bench-5.0.77-4.el5_5.4.ppc.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.ppc.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.ppc64.rpm
mysql-devel-5.0.77-4.el5_5.4.ppc.rpm
mysql-devel-5.0.77-4.el5_5.4.ppc64.rpm
mysql-server-5.0.77-4.el5_5.4.ppc.rpm
mysql-server-5.0.77-4.el5_5.4.ppc64.rpm
mysql-test-5.0.77-4.el5_5.4.ppc.rpm
s390x:
mysql-5.0.77-4.el5_5.4.s390.rpm
mysql-5.0.77-4.el5_5.4.s390x.rpm
mysql-bench-5.0.77-4.el5_5.4.s390x.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.s390.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.s390x.rpm
mysql-devel-5.0.77-4.el5_5.4.s390.rpm
mysql-devel-5.0.77-4.el5_5.4.s390x.rpm
mysql-server-5.0.77-4.el5_5.4.s390x.rpm
mysql-test-5.0.77-4.el5_5.4.s390x.rpm
x86_64:
mysql-5.0.77-4.el5_5.4.i386.rpm
mysql-5.0.77-4.el5_5.4.x86_64.rpm
mysql-bench-5.0.77-4.el5_5.4.x86_64.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.i386.rpm
mysql-debuginfo-5.0.77-4.el5_5.4.x86_64.rpm
mysql-devel-5.0.77-4.el5_5.4.i386.rpm
mysql-devel-5.0.77-4.el5_5.4.x86_64.rpm
mysql-server-5.0.77-4.el5_5.4.x86_64.rpm
mysql-test-5.0.77-4.el5_5.4.x86_64.rpm
These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from
https://www.redhat.com/security/team/key/#package
7. References:
https://www.redhat.com/security/data/cve/CVE-2010-3677.html
https://www.redhat.com/security/data/cve/CVE-2010-3680.html
https://www.redhat.com/security/data/cve/CVE-2010-3681.html
https://www.redhat.com/security/data/cve/CVE-2010-3682.html
https://www.redhat.com/security/data/cve/CVE-2010-3833.html
https://www.redhat.com/security/data/cve/CVE-2010-3835.html
https://www.redhat.com/security/data/cve/CVE-2010-3836.html
https://www.redhat.com/security/data/cve/CVE-2010-3837.html
https://www.redhat.com/security/data/cve/CVE-2010-3838.html
https://www.redhat.com/security/data/cve/CVE-2010-3839.html
https://www.redhat.com/security/data/cve/CVE-2010-3840.html
http://www.redhat.com/security/updates/classification/#moderate
8. Contact:
The Red Hat security contact is <secalert@redhat.com>. More contact
details at https://www.redhat.com/security/team/contact/
Copyright 2010 Red Hat, Inc.
