Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2012-2749: MySQL 5.1.x before 5.1.63 and 5.5.x before 5.5.24 allows remote authenticated users to cause a denial of servi

39
Routine
MEDIUM 4.0WATCHLISTDOWNGRADEDOWNGRADE

CVE-2012-2749 is a medium-severity flaw (CVSS 4.0) affecting mysql, mysql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

MySQL 5.1.x before 5.1.63 and 5.5.x before 5.5.24 allows remote authenticated users to cause a denial of service (mysqld crash) via vectors related to incorrect calculation and a sort order index.

Why this priority

  • On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score4.0 (Medium)
EPSS exploit chance1.9% (top 20%)
CISA exploited listNo
WeaknessCWE-399
Published2012-08-17
Last modified2026-06-16
Publisher (CNA): Red Hat, Inc. · Vendor: mysql · oracle

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

mysql mysql DOWNGRADE
Affected: 5.1.5 · 5.1.23 · 5.1.31 · 5.1.32 · 5.1.34 · 5.1.37
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.1.5
1. Check installed version
apt-cache policy mysql || rpm -q mysql || mysql --version
2. No fixed release: DOWNGRADE to a release before 5.1.5 (Debian / Ubuntu)
apt-cache madison mysql sudo apt install mysql=<VERSION_BEFORE_5.1.5> sudo apt-mark hold mysql
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mysql sudo dnf downgrade mysql-<VERSION_BEFORE_5.1.5> sudo dnf versionlock add mysql
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle mysql DOWNGRADE
Affected: 5.1 · 5.1.1 · 5.1.2 · 5.1.3 · 5.1.4 · 5.1.6 · 5.1.7 · 5.1.8
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.1
1. Check installed version
apt-cache policy mysql || rpm -q mysql || mysql --version
2. No fixed release: DOWNGRADE to a release before 5.1 (Debian / Ubuntu)
apt-cache madison mysql sudo apt install mysql=<VERSION_BEFORE_5.1> sudo apt-mark hold mysql
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mysql sudo dnf downgrade mysql-<VERSION_BEFORE_5.1> sudo dnf versionlock add mysql
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2012-2749?

mysql: downgrade or apply the listed mitigation; mysql: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2012-2749 being exploited?

CVE-2012-2749 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2012-2749 affect?

CVE-2012-2749 affects mysql, mysql. Severity is medium (CVSS 4.0). MySQL 5.1.x before 5.1.63 and 5.5.x before 5.5.24 allows remote authenticated users to cause a denial of service (mysqld crash) via vectors related to incorrect calculation and a sort order index.

How urgent is CVE-2012-2749?

Priority 39/100. On your watchlist

Software pages

MySQL vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.