dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2013-0384

MEDIUM · 6.8 CVSS v2.0 Published 2013-01-17
Fix available
A fix is available. Upgrade to 5.1.67 / 5.2.14 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 the Server component in Oracle MySQL 5.1.66 and earlier, and 5.5.28 and earlier, allows remote authenticated users to affect availability via unknown vectors related to Information Schema.

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

A vulnerability in Oracle MySQL Server's Information Schema component allows remote authenticated users to cause a denial of service. The specific vulnerability mechanism is unspecified in the available description, but targets the virtual database that stores metadata about other databases.

MitigationUpdate MySQL to version 5.1.67 or later for the 5.1 branch, or 5.5.29 or later for the 5.5 branch to obtain the vendor patch.

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.1.0, <= 5.1.66>= 5.5.0, <= 5.5.28
Ubuntu LinuxOperating system
Affected:= 10.04= 11.10= 12.04= 12.10
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux EusOperating system
Affected:= 6.3
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
MariaDBDatabase / datastore
Affected:>= 5.1.0, < 5.1.67>= 5.2.0, < 5.2.14>= 5.3.0, < 5.3.12>= 5.5.0, < 5.5.29= 10.0.0

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. Identify if MySQL or MariaDB is installed
    Run 'mysql --version' or 'mysqld --version' from the command line to display the installed database server version
    Affected if No MySQL or MariaDB server is found, then the system is not affected by this CVE
  2. Verify the exact installed version
    Connect to MySQL and run 'SELECT VERSION();' or check the package manager output (dpkg -l mysql-server or rpm -qa | grep mysql)
    Affected if The version falls within the affected ranges: MySQL 5.1.0-5.1.66, 5.5.0-5.5.28; MariaDB 5.1.0-5.1.66, 5.2.0-5.2.13, 5.3.0-5.3.11, 5.5.0-5.5.28, or 10.0.0
  3. Confirm Information Schema is accessible
    Connect to MySQL and run 'SELECT COUNT(*) FROM INFORMATION_SCHEMA.TABLES;' - this verifies the Information Schema virtual database is operational
    Affected if The query returns a count successfully, indicating the vulnerable component is active (this is the default state in MySQL)
  4. Check for remote authentication enabled
    Review MySQL configuration files (my.cnf or my.ini) for 'bind-address' settings and verify user accounts with host permissions allowing remote connections (SELECT user,host FROM mysql.user WHERE host NOT IN ('localhost','127.0.0.1'));
    Affected if Remote authentication is enabled and user accounts permit remote connections - the CVE can be exploited by remote authenticated attackers

A system is affected if it runs any MySQL or MariaDB version within the specified vulnerable ranges AND has the Information Schema accessible (default state) AND allows remote authenticated access.

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 5.1.67 / 5.2.14 / 5.3.12 or later
Fixed in 5.1.675.2.145.3.12
Interim mitigation

Update MySQL to version 5.1.67 or later for the 5.1 branch, or 5.5.29 or later for the 5.5 branch to obtain the vendor patch.

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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