MySQLDatabase / datastore · Oracle
CVE-2014-4258
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 the MySQL Server component in Oracle MySQL 5.5.37 and earlier and 5.6.17 and earlier allows remote authenticated users to affect confidentiality, integrity, and availability via vectors related to SRINFOSC.
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 confidenceMemory corruption or improper access control vulnerability in Oracle MySQL Server versions 5.5.37 and earlier and 5.6.17 and earlier, specifically within the SRINFOSC (Server Information/OSC) component. Exploitable by remote authenticated users, allowing impact to confidentiality, integrity, and availability with medium complexity.
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.37>= 5.6.0, <= 5.6.17
Vcenter Server ApplianceApplication
= 5.0= 5.1= 5.5
Debian LinuxOperating system
= 7.0
MariaDBDatabase / datastore
>= 5.5.0, < 5.5.38>= 10.0.0, < 10.0.12= 11.3= 11.0= 11.0= 11.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.
-
Identify MySQL or MariaDB versionRun 'mysql --version' or 'mysqld --version' to get the installed database server versionAffected if Version falls within 5.5.0-5.5.37 or 5.6.0-5.6.17 for MySQL; or 5.5.0-5.5.37 or 10.0.0-10.0.11 for MariaDB
-
Check for MySQL Enterprise Monitor installationLook for MySQL Enterprise Monitor components: check for 'mysql-monitor' or 'enterprise-monitor' processes via 'ps aux | grep -i mysql' or check for installation directories like /opt/mysql/enterprise/Affected if MySQL Enterprise Monitor is installed and the SRINFOSC component is present
-
Verify SRINFOSC component statusIf MySQL Enterprise Monitor is present, check if the SRINFOSC (Server Information/OSC) service is running - look for osc or srinfosc in process list or service statusAffected if SRINFOSC component is installed and actively running
-
For VMware environments, check vCenter Server Appliance versionAccess vCenter admin interface or run 'vpxd -v' from appliance console to get versionAffected if VMware vCenter Server Appliance version is 5.0, 5.1, or 5.5
Environment is affected if running a vulnerable MySQL/MariaDB version AND the SRINFOSC component from MySQL Enterprise Monitor is installed and enabled, or if using vulnerable VMware vCenter Server Appliance versions.
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.3810.0.12
Upgrade MySQL Server to version 5.5.38 or later, or 5.6.18 or later. If immediate upgrade is not possible, restrict network access to MySQL and enforce least-privilege user accounts.
Fix this in MySQL
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4258 — 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-4258 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