dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2016-0652

MEDIUM · 5.5 CVSS v3.0 Published 2016-04-21
Fix available
A fix is available. Upgrade to after 5.7.10 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Unspecified vulnerability in Oracle MySQL 5.7.10 and earlier allows local users to affect availability via vectors related to DML.

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

Local privilege vulnerability in Oracle MySQL 5.7.10 and earlier allowing local users to impact availability through unspecified DML operations. The exact exploitation vector and impact mechanism are not detailed in the public advisory.

MitigationUpgrade MySQL to version 5.7.11 or later to obtain the security patch. If immediate upgrade is not feasible, restrict local database user privileges and monitor for suspicious DML operations.

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.7.10

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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. Verify MySQL is installed
    Run 'mysql --version' or check for the mysql service/process on the system using 'systemctl status mysql' or 'service mysql status'
    Affected if MySQL server is running on the system
  2. Determine the exact MySQL version
    Connect to MySQL and run 'SELECT VERSION();' or use 'mysqladmin version' from command line
    Affected if The version returned is 5.7.10 or any earlier 5.7.x release
  3. Check MySQL service account privileges
    Review local system user privileges for the mysql service account and any database users with local access
    Affected if Local users have elevated database privileges beyond standard requirements
  4. Review database user permissions
    Connect to MySQL and run 'SELECT user, host, plugin FROM mysql.user;' to enumerate user accounts
    Affected if Local system users have unnecessary privileges granted

A system is affected if MySQL 5.7.10 or earlier is installed and running, particularly if local system users have database access permissions.

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
Upgrade available Upgrade to a release after 5.7.10
Interim mitigation

Upgrade MySQL to version 5.7.11 or later to obtain the security patch. If immediate upgrade is not feasible, restrict local database user privileges and monitor for suspicious DML operations.

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-0652 — 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-2016-0652 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