MySQLDatabase / datastore · Oracle
CVE-2013-1552
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 Oracle MySQL 5.1.67 and earlier and 5.5.29 and earlier allows remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors.
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 5.1.67 and earlier and 5.5.29 and earlier allowing remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors. The 'unspecified' nature means exact technical details are not provided, but the CVSS indicates a server-side vulnerability requiring authentication.
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.1.0, <= 5.1.67>= 5.5.0, <= 5.5.29
MariaDBDatabase / datastore
>= 5.5.0, < 5.5.30>= 10.0.0, < 10.0.2
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux EusOperating system
= 6.4
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux Server AusOperating system
= 6.4
Enterprise Linux WorkstationOperating system
= 6.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 installed MySQL versionRun `mysql --version` or `mysqld --version` from command line, or query `SELECT VERSION();` inside the MySQL clientAffected if Version is between 5.1.0 and 5.1.67 inclusive, or between 5.5.0 and 5.5.29 inclusive
-
Identify installed MariaDB versionRun `mariadb --version` or `mysql --version` from command line, or query `SELECT VERSION();` inside the MariaDB clientAffected if Version is 5.5.0 through 5.5.29, or 10.0.0 through 10.0.1
-
Check Red Hat Enterprise Linux versionRun `cat /etc/redhat-release` to confirm the RHEL versionAffected if Version is exactly 6.0, 6.4, or derivatives like Desktop/Eus/Server Aus/Workstation matching those releases
-
Determine if network access to MySQL/MariaDB is enabledCheck MySQL configuration files for `bind-address` setting and review firewall rules or port 3306 listening status using `netstat -tulpn | grep 3306`Affected if The database server is listening on network interfaces and is accessible remotely - this indicates the attack surface for authenticated remote exploits
You are affected if your installed MySQL version is 5.1.67 or earlier, or 5.5.29 or earlier, or your MariaDB version is below 5.5.30 or below 10.0.2, running on the listed RHEL 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.3010.0.2
Upgrade MySQL to version 5.1.68 or higher, or 5.5.30 or higher to remediate this vulnerability. If immediate upgrade is not feasible, restrict network access to MySQL servers and ensure strong authentication mechanisms are in place.
Fix this in MySQL
Scoped from the published advisory
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1552 — 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-1552 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