MySQLDatabase / datastore
CVE-2013-1492
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 · uneditedBuffer overflow in yaSSL, as used in MySQL 5.1.x before 5.1.68 and 5.5.x before 5.5.30, has unspecified impact and attack vectors, a different vulnerability than CVE-2012-0553.
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 confidenceBuffer overflow vulnerability in the yaSSL library bundled with MySQL versions 5.1.x before 5.1.68 and 5.5.x before 5.5.30. The vulnerability has high severity (CVSS 7.5) and is exploitable over the network without authentication, potentially allowing remote code execution or service disruption.
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
= 5.1.5= 5.1.23= 5.1.31= 5.1.32= 5.1.34= 5.1.37
MySQLDatabase / datastore
= 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.12CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed MySQL versionRun `mysql --version` or log into MySQL and execute `SELECT VERSION();`Affected if Version is 5.1.x before 5.1.68 or 5.5.x before 5.5.30
-
Verify MySQL server is network accessibleCheck if MySQL port (default 3306) is listening on an interface other than localhost using `netstat -tlnp | grep 3306` or `ss -tlnp | grep 3306`Affected if MySQL is bound to 0.0.0.0 or a publicly accessible IP address
-
Confirm SSL/TLS usage in MySQLCheck MySQL configuration files (my.cnf or my.ini) for SSL-related settings, or query with `SHOW VARIABLES LIKE 'have_ssl';`Affected if SSL is enabled (have_ssl=YES) on an affected version
-
Check yaSSL library presenceLocate yaSSL files in MySQL installation directory, typically under lib/plugin or lib directory, or search for files containing 'yassl' in the MySQL data or program directoriesAffected if yaSSL library files exist in the MySQL installation
You are affected if MySQL version is 5.1.x before 5.1.68 or 5.5.x before 5.5.30, and the server is network accessible with SSL enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade MySQL to version 5.1.68 or higher, or 5.5.30 or higher. If immediate patching is not feasible, restrict network access to MySQL ports and ensure proper firewall rules are in place.
Fix this in MySQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1492 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-1492 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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