sql/password.c in Oracle MySQL 5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6, and MariaDB 5.1.x…
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw lies in sql/password.c of Oracle MySQL (5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6) and MariaDB (5.1.x before 5.1.62, 5.2.x before 5.2.12, 5.3.x before 5.3.6, and 5.5.x before 5.5.23), where a token comparison relies on an improperly checked return value from memcmp in certain environments. A remote attacker can bypass authentication by repeatedly logging in with the same incorrect password until the comparison succeeds, and this requires that the server run in an environment with a particular memcmp implementation.
Official description · CVE.org
sql/password.c in Oracle MySQL 5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6, and MariaDB 5.1.x before 5.1.62, 5.2.x before 5.2.12, 5.3.x before 5.3.6, and 5.5.x before 5.5.23, when running in certain environments with certain implementations of the memcmp function, allows remote attackers to bypass authentication by repeatedly authenticating with the same incorrect password, which eventually causes a token comparison to succeed due to an improperly-checked return value.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Metasploit) was available 17 days before disclosure.
- Public exploit codeMetasploit17 days before
- Disclosedday 0
What security researchers reported
Not named in any threat report yetAlso mentioned in 2 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- CVE Data16 Feb 2026
- Python: OVSAgentServer Document (autofilled name)5 Jun 2024