dbcve.org
MySQLDatabase / datastore

CVE-2012-0553

HIGH · 7.5 CVSS v2.0 Published 2013-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Buffer overflow vulnerability in the yaSSL library bundled with MySQL 5.1.x before 5.1.68 and 5.5.x before 5.5.28. The flaw resides in the SSL/TLS implementation and allows memory corruption via crafted network packets, potentially enabling remote code execution.

MitigationUpgrade MySQL installations to version 5.1.68+, 5.5.28+, or migrate to newer supported versions (5.6+) that no longer include the vulnerable yaSSL library.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MySQLDatabase / datastore
Affected:= 5.1.5= 5.1.23= 5.1.31= 5.1.32= 5.1.34= 5.1.37
MySQLDatabase / datastore
Affected:= 5.1= 5.1.1= 5.1.2= 5.1.3= 5.1.4= 5.1.6= 5.1.7= 5.1.8= 5.1.9= 5.1.10= 5.1.11= 5.1.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed MySQL version
    Run `mysql --version` from command line or execute `SELECT VERSION();` inside the MySQL client
    Affected if The version is MySQL 5.1.x before 5.1.68, or MySQL 5.5.x before 5.5.28
  2. Confirm SSL/TLS support is enabled
    Check MySQL system variables with `SHOW VARIABLES LIKE 'have_ssl';` or `SHOW VARIABLES LIKE 'ssl%';`
    Affected if The `have_ssl` or `ssl` variable is set to YES or enabled (the vulnerability resides in the SSL/TLS implementation)
  3. Verify MySQL listens on network interfaces
    Check configuration with `SHOW VARIABLES LIKE 'bind_address';` or review my.cnf for network bind settings
    Affected if MySQL binds to a reachable network address (0.0.0.0 or specific IP) rather than localhost only, as exploitation requires receiving crafted network packets

You are affected if your MySQL version falls within 5.1.x before 5.1.68 or 5.5.x before 5.5.28, SSL/TLS is enabled, and the server accepts remote connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MySQL installations to version 5.1.68+, 5.5.28+, or migrate to newer supported versions (5.6+) that no longer include the vulnerable yaSSL library.

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0553 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0553 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data