Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2012-0553: Buffer overflow in yaSSL, as used in MySQL 5.1.x before 5.1.68 and 5.5.x before 5.5.28, has unspecified impact

53
This month
HIGH 7.5WATCHLISTDOWNGRADEDOWNGRADE

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

Buffer overflow in yaSSL, as used in MySQL 5.1.x before 5.1.68 and 5.5.x before 5.5.28, has unspecified impact and attack vectors, a different vulnerability than CVE-2013-1492.

Why this priority

  • High severity
  • On your watchlist

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

Risk facts

CVSS score7.5 (High)
EPSS exploit chance2.6% (top 15%)
CISA exploited listNo
WeaknessCWE-119
Published2013-03-28
Last modified2026-06-16
Publisher (CNA): Oracle · 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-0553?

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-0553 being exploited?

CVE-2012-0553 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-0553 affect?

CVE-2012-0553 affects mysql, mysql. Severity is high (CVSS 7.5). Buffer overflow in yaSSL, as used in MySQL 5.1.x before 5.1.68 and 5.5.x before 5.5.28, has unspecified impact and attack vectors, a different vulnerability than CVE-2013-1492.

How urgent is CVE-2012-0553?

Priority 53/100. High severity; 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.