Home/CVE/Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.1.61 and earlier, and 5.5.21 and earlier, allo
CVE
CVE-2012-17031
Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.1.61 and earlier, and 5.5.21 and earlier, allo
Unspecified 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.
MEDIUM · CVSS 6.8
EPSS 0.0374
EPSS exploitation odds3.74% · top 11%
Schedule remediation
- Public exploit or PoC is available
Sigma rules2
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2012-1703, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⚠
Exploitation evidence
1 of 7 sources
Corroboration score 8/100 ·
emerging.
This counts how many independent sources have exploitation evidence, and separates two different things:
confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from
exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means
an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.
Exploit / PoC available
public PoC
↗
Exploitation momentum
496 days of EPSSdormant
Flat and low - no real exploitation pressure. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
▣
Severity & exploitation scoring
EPSS exploitation probability
3.74%
Top 11%odds of exploitation in the next 30 days
CVSS metric silhouette
No structured CVSS vector for this CVE. Older entries often have only a numeric base score - the metric breakdown radar requires a full
AV:_/AC:_/... vector string published by NVD.SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
Lifecycle
- 03 May 2012Published to NVD
- 16 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
⚠
Public Exploits & PoCs
1These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
Source
Works?
no reports yet
Rating
◆
ATT&CK techniques
1Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques▤
Affected Products & Versions
9oracle mysql>= 5.1.0 and <= 5.1.61
oracle mysql>= 5.5.0 and <= 5.5.21
redhat enterprise linux desktopall versions
redhat enterprise linux hpc nodeall versions
redhat enterprise linux serverall versions
redhat enterprise linux server eusall versions
redhat enterprise linux workstationall versions
mariadb>= 5.1.0 and < 5.1.62
mariadb>= 5.5.0 and < 5.5.22
▤
Related CVEs
6CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2005-0004
The mysqlaccess script in MySQL 4.0.23 and earlier, 4.1.x before 4.1.10, 5.0.x b...
same product
CVE-2009-4484
Multiple stack-based buffer overflows in the CertDecoder::GetName function in sr...
1
same product
CVE-2010-5298
Race condition in the ssl3_read_bytes function in s3_pkt.c in OpenSSL through 1....
same product
CVE-2012-1688
Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.1.61 a...
same product
CVE-2012-1690
Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.1.61 a...
same product
CVE-2012-1697
Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.5.21 a...
same product
📦
Fixed versions by distribution
8The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle allmysql fixed in 0:5.1.66-1.el6_3
oracle allmysql-bench fixed in 0:5.1.66-1.el6_3
oracle allmysql-devel fixed in 0:5.1.66-1.el6_3
oracle allmysql-embedded open
oracle allmysql-embedded-devel open
oracle allmysql-libs open
oracle allmysql-server open
oracle allmysql-test fixed in 0:5.1.66-1.el6_3
◈
Sigma Hunt Rules
2Exact rules name this CVE ID. Product rules name an affected product in their title. Related rules cover techniques used by actors who exploited this CVE. Showing the most relevant matches; the complete related set is on the full drill-down.
⚑
Vendor Advisories
1🔗
References & Sources
10Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.