dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2000-0148

HIGH · 7.5 CVSS v2.0 Published 2000-02-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
MySQL 3.22 allows remote attackers to bypass password authentication and access a database via a short check string.

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 confidence

MySQL 3.22 contains an authentication bypass vulnerability allowing remote attackers to circumvent password verification through a specially crafted short check string, granting unauthorized access to databases without valid credentials.

MitigationUpgrade from MySQL 3.22 to a patched version (3.23+) or migrate to a currently supported MySQL/MariaDB release, as version 3.22 is obsolete and no longer receives security updates.

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
Affected:= 3.22.26= 3.22.27= 3.22.29= 3.22.30= 3.23.8= 3.23.9= 3.23.10

CVSS 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
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Retrieve installed MySQL version
    Run 'mysql --version' or 'mysqld --version' from command line, or query 'SELECT VERSION();' inside the MySQL client
    Affected if The version displayed matches any of: 3.22.26, 3.22.27, 3.22.29, 3.22.30, 3.23.8, 3.23.9, or 3.23.10
  2. Confirm MySQL server is reachable
    Attempt to connect to the MySQL service on the target host using 'mysql -h <host> -u <user>' or verify the service is listening on port 3306
    Affected if The MySQL server accepts connections and responds with a version matching the affected list
  3. Verify authentication behavior (optional probe)
    If feasible in your environment, attempt a connection with an invalid password to observe if authentication is enforced; otherwise, rely on version check alone
    Affected if Authentication fails to properly reject invalid credentials, indicating potential bypass capability - but this should only be done in authorized, non-production testing

A user is affected if their MySQL installation reports a version matching exactly one of: 3.22.26, 3.22.27, 3.22.29, 3.22.30, 3.23.8, 3.23.9, or 3.23.10.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade from MySQL 3.22 to a patched version (3.23+) or migrate to a currently supported MySQL/MariaDB release, as version 3.22 is obsolete and no longer receives security updates.

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2000-0148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2000-0148 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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