MySQLDatabase / datastore · Oracle
CVE-2012-4414
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 · uneditedMultiple SQL injection vulnerabilities in the replication code in Oracle MySQL possibly before 5.5.29, and MariaDB 5.1.x through 5.1.62, 5.2.x through 5.2.12, 5.3.x through 5.3.7, and 5.5.x through 5.5.25, allow remote authenticated users to execute arbitrary SQL commands via vectors related to the binary log. NOTE: as of 20130116, Oracle has not commented on claims from a downstream vendor that the fix in MySQL 5.5.29 is incomplete.
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 · high confidenceSQL injection vulnerabilities exist in the replication code of MySQL and MariaDB, specifically in functionality related to the binary log. Remote authenticated users can exploit these flaws to execute arbitrary SQL commands. The issue affects MariaDB versions 5.1.x through 5.1.62, 5.2.x through 5.2.12, 5.3.x through 5.3.7, and 5.5.x through 5.5.25, and possibly MySQL versions prior to 5.5.29.
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.5.28= 5.1.51= 5.1.52= 5.1.53= 5.1.54= 5.1.55= 5.1.56= 5.1.57= 5.1.58= 5.1.59= 5.1.60= 5.1.61
MariaDBDatabase / datastore
= 5.1.41= 5.1.42= 5.1.44= 5.1.47= 5.1.49= 5.1.50= 5.1.51= 5.1.53= 5.1.55= 5.1.60= 5.1.61= 5.1.62CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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.
-
Check MySQL/MariaDB versionRun `mysql --version` from command line or execute `SELECT VERSION();` in mysql clientAffected if Version matches MariaDB 5.1.41-5.1.62, 5.2.x-5.2.12, 5.3.x-5.3.7, 5.5.x-5.5.25 OR MySQL 5.1.51-5.1.61, or MySQL 5.5.0-5.5.28 (or if version cannot be determined)
-
Verify binary logging is enabledExecute `SHOW VARIABLES LIKE 'log_bin';` in mysql clientAffected if Value is ON - the vulnerability exists in binary log replication code
-
Confirm replication is configuredExecute `SHOW SLAVE STATUS\G` and `SHOW MASTER STATUS;` in mysql clientAffected if Replication is actively configured with master/slave relationships, as the flaw is in replication functionality
-
Check for remote authenticated accessReview `SELECT user, host FROM mysql.user;` and identify accounts accessible from non-localhost hostsAffected if Remote authenticated users exist with access to database, as remote authenticated attackers can exploit this flaw
Environment is affected if running a vulnerable MySQL/MariaDB version AND binary logging is enabled AND remote authenticated users can connect.
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.5.29 or later, or MariaDB to a version beyond the affected ranges (5.1.63+, 5.2.13+, 5.3.8+, 5.5.26+). Restrict replication user access and network exposure as a compensating control until patching is complete.
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-2012-4414 — 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-2012-4414 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