ID CVE-2012-2102
Summary MySQL 5.1.x before 5.1.62 and 5.5.x before 5.5.22 allows remote authenticated users to cause a denial of service (assertion failure and mysqld abort) by deleting a record and using HANDLER READ NEXT.
References
Vulnerable Configurations
  • MySQL 5.1.43 Service Pack 1
    cpe:2.3:a:mysql:mysql:5.1.43:sp1
  • MySQL 5.1.33
    cpe:2.3:a:mysql:mysql:5.1.33
  • MySQL 5.1.46 Service Pack 1
    cpe:2.3:a:mysql:mysql:5.1.46:sp1
  • MySQL 5.1.32
    cpe:2.3:a:mysql:mysql:5.1.32
  • MySQL 5.1.47
    cpe:2.3:a:mysql:mysql:5.1.47
  • MySQL 5.1.31
    cpe:2.3:a:mysql:mysql:5.1.31
  • MySQL 5.1.23a
    cpe:2.3:a:mysql:mysql:5.1.23:a
  • Oracle MySQL 5.1.60
    cpe:2.3:a:oracle:mysql:5.1.60
  • MySQL 5.1.23_bk
    cpe:2.3:a:mysql:mysql:5.1.23_bk
  • Oracle MySQL 5.1.61
    cpe:2.3:a:oracle:mysql:5.1.61
  • Oracle MySQL 5.1.58
    cpe:2.3:a:oracle:mysql:5.1.58
  • Oracle MySQL 5.1.59
    cpe:2.3:a:oracle:mysql:5.1.59
  • Oracle MySQL 5.1.56
    cpe:2.3:a:oracle:mysql:5.1.56
  • Oracle MySQL 5.1.57
    cpe:2.3:a:oracle:mysql:5.1.57
  • Oracle MySQL 5.1.54
    cpe:2.3:a:oracle:mysql:5.1.54
  • Oracle MySQL 5.1.55
    cpe:2.3:a:oracle:mysql:5.1.55
  • Oracle MySQL 5.1.52 Service Pack 1
    cpe:2.3:a:oracle:mysql:5.1.52:sp1
  • Oracle MySQL 5.1.53
    cpe:2.3:a:oracle:mysql:5.1.53
  • Oracle MySQL 5.1.51
    cpe:2.3:a:oracle:mysql:5.1.51
  • Oracle MySQL 5.1.52
    cpe:2.3:a:oracle:mysql:5.1.52
  • MySQL 5.1.42
    cpe:2.3:a:mysql:mysql:5.1.42
  • MySQL 5.1.43
    cpe:2.3:a:mysql:mysql:5.1.43
  • MySQL 5.1.44
    cpe:2.3:a:mysql:mysql:5.1.44
  • MySQL 5.1.34
    cpe:2.3:a:mysql:mysql:5.1.34
  • MySQL 5.1.35
    cpe:2.3:a:mysql:mysql:5.1.35
  • MySQL 5.1.48
    cpe:2.3:a:mysql:mysql:5.1.48
  • MySQL 5.1.36
    cpe:2.3:a:mysql:mysql:5.1.36
  • MySQL 5.1.37
    cpe:2.3:a:mysql:mysql:5.1.37
  • MySQL 5.1.38
    cpe:2.3:a:mysql:mysql:5.1.38
  • MySQL 5.1.39
    cpe:2.3:a:mysql:mysql:5.1.39
  • MySQL 5.1.40
    cpe:2.3:a:mysql:mysql:5.1.40
  • MySQL 5.1.41
    cpe:2.3:a:mysql:mysql:5.1.41
  • MySQL 5.1.23
    cpe:2.3:a:mysql:mysql:5.1.23
  • MySQL 5.1.5
    cpe:2.3:a:mysql:mysql:5.1.5
  • MySQL 5.1.6
    cpe:2.3:a:mysql:mysql:5.1.6
  • MySQL 5.1.3
    cpe:2.3:a:mysql:mysql:5.1.3
  • MySQL 5.1.4
    cpe:2.3:a:mysql:mysql:5.1.4
  • MySQL 5.1.9
    cpe:2.3:a:mysql:mysql:5.1.9
  • MySQL 5.1.7
    cpe:2.3:a:mysql:mysql:5.1.7
  • MySQL 5.1.8
    cpe:2.3:a:mysql:mysql:5.1.8
  • MySQL 5.1.45
    cpe:2.3:a:mysql:mysql:5.1.45
  • MySQL 5.1.13
    cpe:2.3:a:mysql:mysql:5.1.13
  • MySQL 5.1.14
    cpe:2.3:a:mysql:mysql:5.1.14
  • MySQL 5.1.11
    cpe:2.3:a:mysql:mysql:5.1.11
  • MySQL 5.1.12
    cpe:2.3:a:mysql:mysql:5.1.12
  • MySQL 5.1.17
    cpe:2.3:a:mysql:mysql:5.1.17
  • MySQL 5.1.2
    cpe:2.3:a:mysql:mysql:5.1.2
  • MySQL 5.1.15
    cpe:2.3:a:mysql:mysql:5.1.15
  • MySQL 5.1.16
    cpe:2.3:a:mysql:mysql:5.1.16
  • MySQL 5.1.30
    cpe:2.3:a:mysql:mysql:5.1.30
  • MySQL 5.1.10
    cpe:2.3:a:mysql:mysql:5.1.10
  • MySQL 5.1
    cpe:2.3:a:mysql:mysql:5.1
  • MySQL 5.1.32-bzr
    cpe:2.3:a:mysql:mysql:5.1.32-bzr
  • MySQL 5.1.1
    cpe:2.3:a:mysql:mysql:5.1.1
  • MySQL 5.1.21
    cpe:2.3:a:mysql:mysql:5.1.21
  • MySQL 5.1.22
    cpe:2.3:a:mysql:mysql:5.1.22
  • MySQL 5.1.23a
    cpe:2.3:a:mysql:mysql:5.1.23a
  • MySQL 5.1.5a
    cpe:2.3:a:mysql:mysql:5.1.5a
  • MySQL 5.1.18
    cpe:2.3:a:mysql:mysql:5.1.18
  • MySQL 5.1.19
    cpe:2.3:a:mysql:mysql:5.1.19
  • MySQL 5.1.20
    cpe:2.3:a:mysql:mysql:5.1.20
  • MySQL 5.1.50
    cpe:2.3:a:mysql:mysql:5.1.50
  • MySQL 5.1.28
    cpe:2.3:a:mysql:mysql:5.1.28
  • MySQL 5.1.49 Service Pack 1
    cpe:2.3:a:mysql:mysql:5.1.49:sp1
  • MySQL 5.1.29
    cpe:2.3:a:mysql:mysql:5.1.29
  • MySQL 5.1.49
    cpe:2.3:a:mysql:mysql:5.1.49
  • MySQL 5.1.46
    cpe:2.3:a:mysql:mysql:5.1.46
  • MySQL 5.1.26
    cpe:2.3:a:mysql:mysql:5.1.26
  • MySQL 5.1.27
    cpe:2.3:a:mysql:mysql:5.1.27
  • MySQL 5.1.37 Service Pack 1
    cpe:2.3:a:mysql:mysql:5.1.37:sp1
  • MySQL 5.1.40 Service Pack 1
    cpe:2.3:a:mysql:mysql:5.1.40:sp1
  • MySQL 5.1.31 Service Pack 1
    cpe:2.3:a:mysql:mysql:5.1.31:sp1
  • MySQL 5.1.34 Service Pack 1
    cpe:2.3:a:mysql:mysql:5.1.34:sp1
  • MySQL 5.1.24
    cpe:2.3:a:mysql:mysql:5.1.24
  • MySQL 5.1.25
    cpe:2.3:a:mysql:mysql:5.1.25
  • Oracle MySQL 5.5.21
    cpe:2.3:a:oracle:mysql:5.5.21
  • MySQL 5.5.9
    cpe:2.3:a:mysql:mysql:5.5.9
  • Oracle MySQL 5.5.20
    cpe:2.3:a:oracle:mysql:5.5.20
  • MySQL 5.5.5
    cpe:2.3:a:mysql:mysql:5.5.5
  • Oracle MySQL 5.5.19
    cpe:2.3:a:oracle:mysql:5.5.19
  • MySQL 5.5.6
    cpe:2.3:a:mysql:mysql:5.5.6
  • Oracle MySQL 5.5.18
    cpe:2.3:a:oracle:mysql:5.5.18
  • MySQL 5.5.7
    cpe:2.3:a:mysql:mysql:5.5.7
  • Oracle MySQL 5.5.17
    cpe:2.3:a:oracle:mysql:5.5.17
  • MySQL 5.5.8
    cpe:2.3:a:mysql:mysql:5.5.8
  • Oracle MySQL 5.5.16
    cpe:2.3:a:oracle:mysql:5.5.16
  • MySQL 5.5.1
    cpe:2.3:a:mysql:mysql:5.5.1
  • Oracle MySQL 5.5.15
    cpe:2.3:a:oracle:mysql:5.5.15
  • MySQL 5.5.2
    cpe:2.3:a:mysql:mysql:5.5.2
  • Oracle MySQL 5.5.14
    cpe:2.3:a:oracle:mysql:5.5.14
  • MySQL 5.5.3
    cpe:2.3:a:mysql:mysql:5.5.3
  • Oracle MySQL 5.5.13
    cpe:2.3:a:oracle:mysql:5.5.13
  • MySQL 5.5.4
    cpe:2.3:a:mysql:mysql:5.5.4
  • Oracle MySQL 5.5.12
    cpe:2.3:a:oracle:mysql:5.5.12
  • Oracle MySQL 5.5.11
    cpe:2.3:a:oracle:mysql:5.5.11
  • Oracle MySQL 5.5.10
    cpe:2.3:a:oracle:mysql:5.5.10
  • MySQL 5.5.0
    cpe:2.3:a:mysql:mysql:5.5.0
CVSS
Base: 3.5 (as of 17-08-2012 - 10:06)
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
Access
VectorComplexityAuthentication
NETWORK MEDIUM SINGLE_INSTANCE
Impact
ConfidentialityIntegrityAvailability
NONE NONE PARTIAL
nessus via4
  • NASL family Amazon Linux Local Security Checks
    NASL id ALA_ALAS-2012-92.NASL
    description A flaw was found in the way MySQL processed HANDLER READ NEXT statements after deleting a record. 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-2012-2102)
    last seen 2019-02-21
    modified 2018-04-18
    plugin id 69699
    published 2013-09-04
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=69699
    title Amazon Linux AMI : mysql51 (ALAS-2012-92)
  • NASL family Databases
    NASL id MYSQL_5_1_62.NASL
    description The version of MySQL 5.1 installed on the remote host is earlier than 5.1.62. It is, therefore, affected by the following vulnerabilities : - An error exists related to the included yaSSL component that could allow arbitrary code execution. (CVE-2012-0882) - Errors exist related to 'Server Optimizer', 'Server DML', 'Partition' and, in combination with InnoDB, 'HANDLER READ NEXT' that could allow denial of service attacks. (CVE-2012-1688, CVE-2012-1690, CVE-2012-1703, CVE-2012-2102)
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 58802
    published 2012-04-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=58802
    title MySQL 5.1 < 5.1.62 Multiple Vulnerabilities
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-2496.NASL
    description Due to the non-disclosure of security patch information from Oracle, we are forced to ship an upstream version update of MySQL 5.1. There are several known incompatible changes, which are listed in /usr/share/doc/mysql-server/NEWS.Debian.gz. Several issues have been discovered in the MySQL database server. The vulnerabilities are addressed by upgrading MySQL to a new upstream version, 5.1.63, which includes additional changes, such as performance improvements and corrections for data loss defects. These changes are described in the MySQL release notes. CVE-2012-2122, an authentication bypass vulnerability, occurs only when MySQL has been built in with certain optimisations enabled. The packages in Debian stable (squeeze) are not known to be affected by this vulnerability. It is addressed in this update nonetheless, so future rebuilds will not become vulnerable to this issue.
    last seen 2019-02-21
    modified 2018-11-19
    plugin id 59774
    published 2012-06-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=59774
    title Debian DSA-2496-1 : mysql-5.1 - several vulnerabilities
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2012-0874.NASL
    description Updated mysql packages that fix one security issue and add one enhancement are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries. A flaw was found in the way MySQL processed HANDLER READ NEXT statements after deleting a record. 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-2012-2102) This update also adds the following enhancement : * The InnoDB storage engine is built-in for all architectures. This update adds InnoDB Plugin, the InnoDB storage engine as a plug-in for the 32-bit x86, AMD64, and Intel 64 architectures. The plug-in offers additional features and better performance than when using the built-in InnoDB storage engine. Refer to the MySQL documentation, linked to in the References section, for information about enabling the plug-in. (BZ#740224) All MySQL users should upgrade to these updated packages, which add this enhancement and contain a backported patch to correct this issue. After installing this update, the MySQL server daemon (mysqld) will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 59926
    published 2012-07-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=59926
    title CentOS 6 : mysql (CESA-2012:0874)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2012-0874.NASL
    description Updated mysql packages that fix one security issue and add one enhancement are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries. A flaw was found in the way MySQL processed HANDLER READ NEXT statements after deleting a record. 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-2012-2102) This update also adds the following enhancement : * The InnoDB storage engine is built-in for all architectures. This update adds InnoDB Plugin, the InnoDB storage engine as a plug-in for the 32-bit x86, AMD64, and Intel 64 architectures. The plug-in offers additional features and better performance than when using the built-in InnoDB storage engine. Refer to the MySQL documentation, linked to in the References section, for information about enabling the plug-in. (BZ#740224) All MySQL users should upgrade to these updated packages, which add this enhancement and contain a backported patch to correct this issue. After installing this update, the MySQL server daemon (mysqld) will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-26
    plugin id 59591
    published 2012-06-20
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=59591
    title RHEL 6 : mysql (RHSA-2012:0874)
  • NASL family Databases
    NASL id MYSQL_5_5_22.NASL
    description The version of MySQL 5.5 installed on the remote host is earlier than 5.5.22. It is, therefore, affected by the following vulnerabilities : - An error exists related to the included yaSSL component that could allow arbitrary code execution. (CVE-2012-0882) - Errors exist related to 'Server Optimizer', 'Server DML', 'Partition' and, in combination with InnoDB, 'HANDLER READ NEXT' that could allow denial of service attacks. (CVE-2012-1688, CVE-2012-1690, CVE-2012-1697, CVE-2012-1703, CVE-2012-2102)
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 58661
    published 2012-04-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=58661
    title MySQL 5.5 < 5.5.22 Multiple Vulnerabilities
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20120620_MYSQL_ON_SL6_X.NASL
    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. A flaw was found in the way MySQL processed HANDLER READ NEXT statements after deleting a record. 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-2012-2102) This update also adds the following enhancement : - The InnoDB storage engine is built-in for all architectures. This update adds InnoDB Plugin, the InnoDB storage engine as a plug-in for the 32-bit x86, AMD64, and Intel 64 architectures. The plug-in offers additional features and better performance than when using the built-in InnoDB storage engine. Refer to the MySQL documentation, linked to in the References section, for information about enabling the plug-in. All MySQL users should upgrade to these updated packages, which add this enhancement and contain a backported patch to correct this issue. After installing this update, the MySQL server daemon (mysqld) will be restarted automatically.
    last seen 2019-02-21
    modified 2018-12-31
    plugin id 61341
    published 2012-08-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=61341
    title Scientific Linux Security Update : mysql on SL6.x i386/x86_64
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2012-0874.NASL
    description From Red Hat Security Advisory 2012:0874 : Updated mysql packages that fix one security issue and add one enhancement are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries. A flaw was found in the way MySQL processed HANDLER READ NEXT statements after deleting a record. 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-2012-2102) This update also adds the following enhancement : * The InnoDB storage engine is built-in for all architectures. This update adds InnoDB Plugin, the InnoDB storage engine as a plug-in for the 32-bit x86, AMD64, and Intel 64 architectures. The plug-in offers additional features and better performance than when using the built-in InnoDB storage engine. Refer to the MySQL documentation, linked to in the References section, for information about enabling the plug-in. (BZ#740224) All MySQL users should upgrade to these updated packages, which add this enhancement and contain a backported patch to correct this issue. After installing this update, the MySQL server daemon (mysqld) will be restarted automatically.
    last seen 2019-02-21
    modified 2018-07-18
    plugin id 68555
    published 2013-07-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=68555
    title Oracle Linux 6 : mysql (ELSA-2012-0874)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201308-06.NASL
    description The remote host is affected by the vulnerability described in GLSA-201308-06 (MySQL: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in MySQL. Please review the CVE identifiers referenced below for details. Impact : A remote attacker could send a specially crafted request, possibly resulting in execution of arbitrary code with the privileges of the application or a Denial of Service condition. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-11
    plugin id 69508
    published 2013-08-30
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=69508
    title GLSA-201308-06 : MySQL: Multiple vulnerabilities
redhat via4
advisories
bugzilla
id 812431
title CVE-2012-2102 mysql: Server crash on HANDLER READ NEXT after DELETE
oval
AND
  • OR
    • comment Red Hat Enterprise Linux 6 Client is installed
      oval oval:com.redhat.rhsa:tst:20100842001
    • comment Red Hat Enterprise Linux 6 Server is installed
      oval oval:com.redhat.rhsa:tst:20100842002
    • comment Red Hat Enterprise Linux 6 Workstation is installed
      oval oval:com.redhat.rhsa:tst:20100842003
    • comment Red Hat Enterprise Linux 6 ComputeNode is installed
      oval oval:com.redhat.rhsa:tst:20100842004
  • OR
    • AND
      • comment mysql is earlier than 0:5.1.61-4.el6
        oval oval:com.redhat.rhsa:tst:20120874005
      • comment mysql is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20110164006
    • AND
      • comment mysql-bench is earlier than 0:5.1.61-4.el6
        oval oval:com.redhat.rhsa:tst:20120874019
      • comment mysql-bench is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20110164008
    • AND
      • comment mysql-devel is earlier than 0:5.1.61-4.el6
        oval oval:com.redhat.rhsa:tst:20120874009
      • comment mysql-devel is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20110164016
    • AND
      • comment mysql-embedded is earlier than 0:5.1.61-4.el6
        oval oval:com.redhat.rhsa:tst:20120874013
      • comment mysql-embedded is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20110164010
    • AND
      • comment mysql-embedded-devel is earlier than 0:5.1.61-4.el6
        oval oval:com.redhat.rhsa:tst:20120874017
      • comment mysql-embedded-devel is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20110164020
    • AND
      • comment mysql-libs is earlier than 0:5.1.61-4.el6
        oval oval:com.redhat.rhsa:tst:20120874007
      • comment mysql-libs is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20110164014
    • AND
      • comment mysql-server is earlier than 0:5.1.61-4.el6
        oval oval:com.redhat.rhsa:tst:20120874015
      • comment mysql-server is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20110164012
    • AND
      • comment mysql-test is earlier than 0:5.1.61-4.el6
        oval oval:com.redhat.rhsa:tst:20120874011
      • comment mysql-test is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20110164018
rhsa
id RHSA-2012:0874
released 2012-06-20
severity Low
title RHSA-2012:0874: mysql security and enhancement update (Low)
rpms
  • mysql-0:5.1.61-4.el6
  • mysql-bench-0:5.1.61-4.el6
  • mysql-devel-0:5.1.61-4.el6
  • mysql-embedded-0:5.1.61-4.el6
  • mysql-embedded-devel-0:5.1.61-4.el6
  • mysql-libs-0:5.1.61-4.el6
  • mysql-server-0:5.1.61-4.el6
  • mysql-test-0:5.1.61-4.el6
refmap via4
bid 52931
confirm
gentoo GLSA-201308-06
misc
mlist [oss-security] 20120413 Re: CVE request: mysql: Server crash on HANDLER READ NEXT after DELETE
secunia 53372
Last major update 20-02-2014 - 23:50
Published 16-08-2012 - 20:55
Back to Top