dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2013-2395

MEDIUM · 6.8 CVSS v2.0 Published 2013-04-17
Fix available
A fix is available. Upgrade to after 5.6.10 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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.6.10 and earlier allows remote authenticated users to affect availability via unknown vectors related to Data Manipulation Language, a different vulnerability than CVE-2013-1567.

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

Unspecified vulnerability in Oracle MySQL 5.6.10 and earlier allows remote authenticated users to impact availability via unknown vectors related to Data Manipulation Language (DML) operations. The specific exploitation mechanism and exact code location are not disclosed in available sources.

MitigationApply the Oracle MySQL critical patch update containing the fix for CVE-2013-2395. Additionally, enforce least-privilege database user permissions and restrict network access to MySQL servers to reduce the attack surface for authenticated attackers.

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.6.10= 5.6.0= 5.6.1= 5.6.2= 5.6.3= 5.6.4= 5.6.5= 5.6.6= 5.6.7= 5.6.8= 5.6.9

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
Network
Complexity
Low
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:S/C:N/I:N/A:C

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. Check installed MySQL server version
    Run command: SELECT VERSION(); or mysqld --version
    Affected if Version is 5.6.10 or earlier, including 5.6.0 through 5.6.9
  2. Verify MySQL server is accessible over network
    Check mysqld configuration for bind-address and port 3306 listening status using netstat or ss
    Affected if Server accepts remote connections from untrusted networks
  3. Confirm authenticated access exists
    Review database user privileges and authentication methods: SELECT user, host, plugin FROM mysql.user;
    Affected if Any remote authenticated users or applications have DML privileges (INSERT, UPDATE, DELETE) on database tables

You are affected if your MySQL server version is 5.6.10 or earlier and the server is accessible to remote authenticated users who can execute DML operations.

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.6.10
Interim mitigation

Apply the Oracle MySQL critical patch update containing the fix for CVE-2013-2395. Additionally, enforce least-privilege database user permissions and restrict network access to MySQL servers to reduce the attack surface for authenticated attackers.

Fix this in MySQL Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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