Updated mysql packages that fix multiple security flaws are now available.

This update has been rated as having important security impact by the Red Hat Security Response Team.

MySQL is a multi-user, multi-threaded SQL database server. MySQL is a client/server implementation consisting of a server daemon (mysqld) and many different client programs and libraries.

A flaw was found in the way the MySQL mysql_real_escape() function escaped strings when operating in a multibyte character encoding. An attacker could provide an application a carefully crafted string containing invalidly-encoded characters which may be improperly escaped, leading to the injection of malicious SQL commands.
(CVE-2006-2753)

An information disclosure flaw was found in the way the MySQL server processed malformed usernames. An attacker could view a small portion of server memory by supplying an anonymous login username which was not null terminated. (CVE-2006-1516)

An information disclosure flaw was found in the way the MySQL server executed the COM_TABLE_DUMP command. An authenticated malicious user could send a specially crafted packet to the MySQL server which returned random unallocated memory. (CVE-2006-1517)

A log file obfuscation flaw was found in the way the mysql_real_query() function creates log file entries. An attacker with the the ability to call the mysql_real_query() function against a mysql server can obfuscate the entry the server will write to the log file. However, an attacker needed to have complete control over a server in order to attempt this attack. (CVE-2006-0903)

This update also fixes numerous non-security-related flaws, such as intermittent authentication failures.

All users of mysql are advised to upgrade to these updated packages containing MySQL version 4.1.20, which is not vulnerable to these issues.

远程主机上安装的 MySQL 版本低于 4.1.20 / 5.0.22 / 5.1.11，因此，据报告其允许远程攻击者通过在使用了 mysql_real_escape 时使用多字节字符编码（例如 SJIS、BIG5、GBK）发起 SQL 注入。

遠端主機上安裝的 MySQL 版本比 4.1.20 / 5.0.22 / 5.1.11 舊，因此據報會允許遠端攻擊者在使用 mysql_real_escape 時，可利用多位元組字元編碼 (例如 SJIS、BIG5、GBK) 發動 SQL 插入。

リモートホストにインストールされている MySQL のバージョンは、4.1.20 / 5.0.22 / 5.1.11 以前であるため、mysql_real_escape を使用する際に、リモートの攻撃者がマルチバイト文字エンコーディング（SJIS、BIG5、GBK など）を使用することで、SQL インジェクションを実行できると報告されています。

Josh Berkus and Tom Lane discovered that MySQL 4.1, a popular SQL database, incorrectly parses a string escaped with mysql_real_escape() which could lead to SQL injection. This problem does only exist in versions 4.1 and 5.0.

The remote host is running a version of Mac OS X 10.4 which is older than version 10.4.9 or a version of Mac OS X 10.3 which does not have Security Update 2007-003 applied.

This update contains several security fixes for the following programs :

 - ColorSync
 - CoreGraphics
 - Crash Reporter
 - CUPS
 - Disk Images
 - DS Plugins
 - Flash Player
 - GNU Tar
 - HFS
 - HID Family
 - ImageIO
 - Kernel
 - MySQL server
 - Networking
 - OpenSSH
 - Printing
 - QuickDraw Manager
 - servermgrd
 - SMB File Server
 - Software Update
 - sudo 
 - WebLog

A SQL injection vulnerability has been discovered when using less popular multibyte encodings (such as SJIS, or BIG5) which contain valid multibyte characters that end with the byte 0x5c (the representation of the backslash character >>\<< in ASCII). 

Many client libraries and applications use the non-standard, but popular way of escaping the >>'<< character by replacing all occurences of it with >>\'<<. If a client application uses one of the affected encodings and does not interpret multibyte characters, and an attacker supplies a specially crafted byte sequence as an input string parameter, this escaping method would then produce a validly-encoded character and an excess >>'<< character which would end the string.
All subsequent characters would then be interpreted as SQL code, so the attacker could execute arbitrary SQL commands.

The updated packages fix the mysql_real_escape_string() function to escape quote characters in a safe way. If you use third-party software which uses an ad-hoc method of string escaping, you should convert them to use mysql_real_escape_string() instead, or at least use the standard SQL method of escaping >>'<< with >>''<<.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

New mysql packages are available for Slackware 9.1, 10.0, 10.1, 10.2 and -current to fix security issues. The MySQL packages shipped with Slackware 9.1, 10.0, and 10.1 may possibly leak sensitive information found in uninitialized memory to authenticated users. This is fixed in the new packages, and was already patched in Slackware 10.2 and
-current. Since the vulnerabilities require a valid login and/or access to the database server, the risk is moderate. Slackware does not provide network access to a MySQL database by default.

USN-288-1 described a PostgreSQL client vulnerability in the way the >>'<< character is escaped in SQL queries. It was determined that the PostgreSQL backends of Exim, Dovecot, and Postfix used this unsafe escaping method.

For reference, these are the details of the original USN :

CVE-2006-2313: Akio Ishida and Yasuo Ohgaki discovered a weakness in the handling of invalidly-encoded multibyte text data. If a client application processed untrusted input without respecting its encoding and applied standard string escaping techniques (such as replacing a single quote >>'<< with >>\'<< or >>''<<), the PostgreSQL server could interpret the resulting string in a way that allowed an attacker to inject arbitrary SQL commands into the resulting SQL query. The PostgreSQL server has been modified to reject such invalidly encoded strings now, which completely fixes the problem for some 'safe' multibyte encodings like UTF-8.

CVE-2006-2314: However, there are some less popular and client-only multibyte encodings (such as SJIS, BIG5, GBK, GB18030, and UHC) which contain valid multibyte characters that end with the byte 0x5c, which is the representation of the backslash character >>\<< in ASCII. Many client libraries and applications use the non-standard, but popular way of escaping the >>'<< character by replacing all occurences of it with >>\'<<. If a client application uses one of the affected encodings and does not interpret multibyte characters, and an attacker supplies a specially crafted byte sequence as an input string parameter, this escaping method would then produce a validly-encoded character and an excess >>'<< character which would end the string. All subsequent characters would then be interpreted as SQL code, so the attacker could execute arbitrary SQL commands.

To fix this vulnerability end-to-end, client-side applications must be fixed to properly interpret multibyte encodings and use >>''<< instead of >>\'<<. However, as a precautionary measure, the sequence >>\'<< is now regarded as invalid when one of the affected client encodings is in use. If you depend on the previous behaviour, you can restore it by setting 'backslash_quote = on' in postgresql.conf. However, please be aware that this could render you vulnerable again.

This issue does not affect you if you only use single-byte (like SQL_ASCII or the ISO-8859-X family) or unaffected multibyte (like UTF-8) encodings.

Please see http://www.postgresql.org/docs/techdocs.50 for further details.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The version of MySQL installed on the remote host is earlier than 4.1.20 / 5.0.22 / 5.1.11 and thus reportedly allows a remote attack to launch SQL injections by using multibyte character encodings (e.g. SJIS, BIG5, GBK) when mysql_real_escape is used.

The remote host is affected by the vulnerability described in GLSA-200606-13 (MySQL: SQL Injection)

    MySQL is vulnerable to an injection flaw in mysql_real_escape() when     used with multi-byte characters.
  Impact :

    Due to a flaw in the multi-byte character process, an attacker is still     able to inject arbitary SQL statements into the MySQL server for     execution.
  Workaround :

    There are a few workarounds available: NO_BACKSLASH_ESCAPES mode as a     workaround for a bug in mysql_real_escape_string(): SET     sql_mode='NO_BACKSLASH_ESCAPES'; SET GLOBAL     sql_mode='NO_BACKSLASH_ESCAPES'; and server command line options:
    --sql-mode=NO_BACKSLASH_ESCAPES.

SQL injection vulnerability in MySQL 4.1.x before 4.1.20 and 5.0.x before 5.0.22 allows context-dependent attackers to execute arbitrary SQL commands via crafted multibyte encodings in character sets such as SJIS, BIG5, and GBK, which are not properly handled when the mysql_real_escape function is used to escape the input.

MySQL 4.0.18 in Corporate 3.0 and MNF 2.0 is not affected by this issue.

Packages have been patched to correct this issue.

This update of mysql fixes a bug in the mysql_real_escape() function that allowed SQL command injection (CVE-2006-2753).

The remote host is running a version of Mac OS X 10.4 that is older than version 10.4.9 or a version of Mac OS X 10.3 that does not have Security Update 2007-003 applied. This update contains several security fixes for the following programs :

 - ColorSync
 - CoreGraphics
 - Crash Reporter
 - CUPS
 - Disk Images
 - DS Plugins
 - Flash Player
 - GNU Tar
 - HFS
 - HID Family
 - ImageIO
 - Kernel
 - MySQL server
 - Networking
 - OpenSSH
 - Printing
 - QuickDraw Manager
 - servermgrd
 - SMB File Server
 - Software Update
 - sudo 
 - WebLog

ID	名稱	產品	系列	已發布	已更新	嚴重性
22000	CentOS 4 : mysql (CESA-2006:0544)	Nessus	CentOS Local Security Checks	2006/7/5	2021/1/4	high
21683	RHEL 4 : mysql (RHSA-2006:0544)	Nessus	Red Hat Local Security Checks	2006/6/11	2021/1/14	high
17806	MySQL < 4.1.20 / 5.0.22 / 5.1.11 SQL 注入	Nessus	Databases	2012/1/16	2018/7/16	high
17806	MySQL < 4.1.20 / 5.0.22 / 5.1.11 SQL 插入	Nessus	Databases	2012/1/16	2018/7/16	high
17806	MySQL < 4.1.20 / 5.0.22 / 5.1.11 の SQL インジェクション	Nessus	Databases	2012/1/16	2018/7/16	high
22634	Debian DSA-1092-1 : mysql-dfsg-4.1 - programming error	Nessus	Debian Local Security Checks	2006/10/14	2021/1/4	high
24811	Mac OS X < 10.4.9 Multiple Vulnerabilities (Security Update 2007-003)	Nessus	MacOS X Local Security Checks	2007/3/13	2024/5/28	critical
27878	Ubuntu 5.10 / 6.06 LTS : mysql-dfsg-4.1, mysql-dfsg-5.0 vulnerability (USN-303-1)	Nessus	Ubuntu Local Security Checks	2007/11/10	2021/1/19	high
21639	Slackware 10.0 / 10.1 / 10.2 / 9.1 / current : mysql (SSA:2006-155-01)	Nessus	Slackware Local Security Checks	2006/6/5	2021/1/14	high
27859	Ubuntu 5.04 / 5.10 / 6.06 LTS : dovecot, exim4, postfix vulnerabilities (USN-288-3)	Nessus	Ubuntu Local Security Checks	2007/11/10	2021/1/19	high
17806	MySQL < 4.1.20 / 5.0.22 / 5.1.11 SQL Injection	Nessus	Databases	2012/1/16	2018/7/16	high
21706	GLSA-200606-13 : MySQL: SQL Injection	Nessus	Gentoo Local Security Checks	2006/6/16	2021/1/6	high
21669	Mandrake Linux Security Advisory : MySQL (MDKSA-2006:097)	Nessus	Mandriva Local Security Checks	2006/6/8	2021/1/6	high
27357	openSUSE 10 Security Update : mysql (mysql-1593)	Nessus	SuSE Local Security Checks	2007/10/17	2021/1/14	high
3947	Mac OS X < 10.4.9 Multiple Vulnerabilities (Security Update 2007-003)	Nessus Network Monitor	Web Clients	2007/3/13	2019/3/6	high

偵測

搜尋 Plugin

high

high

high

high

high

high

critical

high

high

high

high

high

high

high

high