MySQLDatabase / datastore · Oracle
CVE-2013-3801
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.30 and earlier and 5.6.10 allows remote authenticated users to affect availability via unknown vectors related to Server Options.
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 confidenceUnspecified vulnerability in Oracle MySQL Server 5.5.30 and earlier/5.6.10 allows remote authenticated users to impact availability through unknown vectors related to Server Options. This is a denial-of-service vulnerability requiring authenticated MySQL access.
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.30>= 5.6.0, <= 5.6.10
MariaDBDatabase / datastore
>= 5.5.0, < 5.5.31>= 10.0.0, < 10.0.3= 11.4= 12.2= 12.3= 11= 11= 11CVSS 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
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 `SELECT VERSION();` as an authenticated userAffected if Version is 5.5.0 through 5.5.30, or 5.6.0 through 5.6.10 for MySQL; or 5.5.0 through 5.5.30, or 10.0.0 through 10.0.2 for MariaDB
-
Check MySQL service statusRun `systemctl status mysql` or `systemctl status mariadb` to confirm the database server is runningAffected if The MySQL/MariaDB service is active and accessible on the network
-
Verify network exposureCheck if port 3306 (default MySQL) is listening on non-localhost interfaces with `netstat -tlnp | grep 3306` or `ss -tlnp | grep 3306`Affected if MySQL is bound to 0.0.0.0 or an external IP, allowing remote connections
-
Confirm authentication methodReview MySQL user table with `SELECT user,host FROM mysql.user;` to see if remote users existAffected if Remote authenticated users can connect (any user with host not limited to localhost)
If the installed MySQL version is between 5.5.0-5.5.30 or 5.6.0-5.6.10 (or MariaDB 5.5.0-5.5.30/10.0.0-10.0.2) AND the service is accessible to authenticated users, the environment is affected by this DoS vulnerability.
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.3110.0.3
Apply Oracle's security patch to update MySQL to a version beyond 5.5.30 and 5.6.10, or upgrade to a currently supported MySQL version with the latest security updates.
Fix this in MySQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3801 — 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-2013-3801 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