MySQLDatabase / datastore · Oracle
CVE-2014-2436
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 · uneditedUnspecified vulnerability in Oracle MySQL Server 5.5.36 and earlier and 5.6.16 and earlier allows remote authenticated users to affect confidentiality, integrity, and availability via vectors related to RBR.
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 confidenceCVE-2014-2436 is an unspecified vulnerability in Oracle MySQL Server versions 5.5.36 and earlier and 5.6.16 and earlier. The flaw resides in the Row-Based Replication (RBR) functionality and allows remote authenticated users to impact confidentiality, integrity, and availability through unspecified vectors.
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.0, <= 5.5.36>= 5.6.0, <= 5.6.16
MariaDBDatabase / datastore
>= 5.5.0, < 5.5.37>= 10.0.0, < 10.0.11
Enterprise Linux DesktopOperating system
= 5.0= 7.0
Enterprise Linux EusOperating system
= 7.3= 7.4= 7.5= 7.6= 7.7
Enterprise Linux ServerOperating system
= 5.0= 7.0
Enterprise Linux Server AusOperating system
= 7.3= 7.4= 7.6= 7.7
Enterprise Linux Server TusOperating system
= 7.3= 7.6= 7.7
Enterprise Linux WorkstationOperating system
= 5.0= 7.0CVSS 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 or MariaDB server versionRun `mysql --version` or connect to MySQL and execute `SELECT VERSION();`Affected if Version is 5.5.36 or earlier for MySQL 5.5 branch, or 5.6.16 or earlier for MySQL 6 branch. For MariaDB, version is below 5.5.37 or below 10.0.11.
-
Confirm Row-Based Replication is in useConnect to MySQL and execute `SHOW REPLIATE STATUS\G` and look for `binlog_format=ROW` in the output, or check my.cnf for `binlog-format=ROW`Affected if The variable `binlog_format` is set to ROW, indicating row-based replication is enabled.
-
Check if replication slave is configuredExecute `SHOW SLAVE STATUS\G` or `SHOW REPLICA STATUS\G` (MySQL 8.0+) and verify the `Slave_IO_Running` and `Slave_SQL_Running` fieldsAffected if A replication slave is configured and running, making RBR active in the environment.
-
Verify MySQL is exposed to remote network accessCheck my.cnf for `bind-address` configuration and confirm the port 3306 (default) is open to network interfaces beyond localhost using tools like `netstat -tlnp | grep 3306`Affected if MySQL is listening on a non-localhost interface, allowing remote authenticated connections.
You are affected if your MySQL version falls within the vulnerable ranges AND Row-Based Replication is enabled AND the server accepts remote authenticated connections.
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 data5.5.3710.0.11
Upgrade MySQL Server to version 5.5.37 or later for the 5.5 branch, or 5.6.17 or later for the 5.6 branch. Alternatively, apply the corresponding Oracle Critical Patch Update from April 2014.
Fix this in MySQL
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2436 — 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-2014-2436 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