S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Network Vulnerabilities·Updated Sep 22, 2026

CVE-2012-2122 Scanner

CVE-2012-2122 Scanner - Authentication Bypass vulnerability in MySQL

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
3
Times Used
continuous scan runs
5.9k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
5.1
CVSS
Description

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.

Attack Vector
-
Privileges Req.
-
User Interaction
-
Affected
n/aby n/a
n/a
Updated Sep 18, 2026View on NVD →
Detail

The scanner is designed to identify a vulnerability in MySQL, a widely used open-source relational database management system (RDBMS) developed by Oracle. MySQL is commonly used by developers and companies worldwide for data storage, website operation, and other database needs. The software is favored due to its balance of speed, reliability, and ease of use. Companies of all sizes from startups to major corporations rely on MySQL for their business-critical applications. It is used across various environments, including cloud-based web applications, enterprise-level software, and personal projects. Knowing the security posture of MySQL installations across networks is essential for database admins and enterprise security teams.

This scanner identifies an Authentication Bypass vulnerability in MySQL, which potentially allows unauthorized access to the database. This vulnerability affects MySQL and MariaDB when operating in particular environments where the memcmp function is improperly handled. Attackers could exploit this issue by repeatedly attempting authentication with incorrect passwords until a successful comparison. The vulnerability exists due to improper return value checking, which can undermine security mechanisms and lead to unauthorized access.

The vulnerability occurs at the point where the MySQL database performs authentication checks, with the vulnerability specifically present in the sql/password.c file. Through incorrect handling of the memcmp return value, repeated incorrect password attempts by a remote attacker can eventually result in successful authentication, breaching the intended security barriers. By exploiting this, attackers could potentially escalate their privileges or access sensitive data within the database without correct credentials.

If exploited, this vulnerability can lead to severe database security breaches, including unauthorized access to confidential information and disruption of database services. Attackers can maneuver around authentication processes, gaining access to sensitive data and potentially compromising other connected systems or applications. This can result in data leaks, integrity issues, and compromise the overall security of applications relying on MySQL.

REFERENCES

Solution Advice
Remediation:
  • Upgrade to MySQL 5.1.63, 5.5.24, 5.6.6 or later versions
  • In case of using MariaDB, upgrade to 5.1.62, 5.2.12, 5.3.6, 5.5.23 or later that properly handle memcmp return values
  • Regularly audit and monitor databases for unauthorized access attempts or anomalies
  • Implement additional authentication layers for critical database operations
  • Conduct regular security assessments and patch management practices to maintain updated software

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.

CVE-2012-2122 Scanner - Authentication Bypass vulnerability in MySQL | S4E