MySQLDatabase / datastore · Oracle
CVE-2012-1703
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.1.61 and earlier, and 5.5.21 and earlier, allows remote authenticated users to affect availability via unknown vectors related to Server Optimizer, a different vulnerability than CVE-2012-1690.
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 confidenceVulnerability in the MySQL Server Optimizer component affecting versions 5.1.61 and earlier, and 5.5.21 and earlier. Allows remote authenticated users to cause availability impact (potential denial of service) through unknown vectors in the query optimizer. Requires authentication to exploit.
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.61>= 5.5.0, <= 5.5.21
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux Hpc NodeOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux Server EusOperating system
= 6.3.z
Enterprise Linux WorkstationOperating system
= 6.0
MariaDBDatabase / datastore
>= 5.1.0, < 5.1.62>= 5.5.0, < 5.5.22CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed MySQL versionRun command: mysql --version or mysqld --version or SELECT VERSION();Affected if Version is 5.1.0 through 5.1.61, or 5.5.0 through 5.5.21
-
Determine installed MariaDB versionRun command: mysql --version or SELECT VERSION();Affected if Version is 5.1.0 through 5.1.61, or 5.5.0 through 5.5.21
-
Check if MySQL service is running and accepting remote connectionsReview mysqld configuration for bind-address and port 3306 exposure; check with: netstat -tlnp | grep 3306Affected if MySQL is listening on a non-localhost interface (0.0.0.0) and is network-accessible
-
Verify if authentication is required for database accessConfirm that the MySQL server enforces password authentication and anonymous accounts are disabled; check with: SELECT user, host FROM mysql.user WHERE authentication_string IS NULL;Affected if Any MySQL accounts allow remote access without authentication or with weak credentials
The environment is affected if the installed MySQL or MariaDB version falls within 5.1.0-5.1.61 or 5.5.0-5.5.21 AND the database is network-accessible with authenticated user access.
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.1.625.5.22
Upgrade MySQL Server to versions beyond 5.1.61 and 5.5.21 (patched versions include 5.1.62+ and 5.5.22+). Alternatively, restrict network access to MySQL and limit privileged database accounts to reduce attack surface.
Fix this in MySQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2012-1703 — 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-2012-1703 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