How severe is CVE-2012-2122?

No CVSS score has been assigned to CVE-2012-2122 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-2122?

Affected package information for CVE-2012-2122 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2012-2122?

No fixed version has been published for CVE-2012-2122 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2012-2122 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2012-2122, including 1 documented proof-of-concept exploit on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2012-2122?

CVE-2012-2122 has an EPSS (Exploit Prediction Scoring System) score of 94.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2012-2122?

CVE-2012-2122 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2012-2122?

CVE-2012-2122 affects mariadb mariadb (33 versions, e.g. 5.1.41, 5.1.42, 5.1.44…); oracle mysql (27 versions, e.g. 5.1.51, 5.1.52, 5.1.53…). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2012-2122 published, and has it been updated?

CVE-2012-2122 was published on June 26, 2012 and was last updated on April 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2012-2122: Mariadb Improper Authentication

EPSS Exploitation Probability

via FIRST.org ↗

94.1%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

2 products · 61 configurations

Application

mariadbmariadb

33 versions

5.1.415.1.425.1.445.1.475.1.495.1.505.1.515.1.535.1.555.1.605.1.615.2.0

Application

mysqloracle

27 versions

5.1.515.1.525.1.535.1.545.1.555.1.565.1.575.1.585.1.595.1.605.1.615.5.10

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2012-2122 in your stack?

O3 detects CVE-2012-2122 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works