CVE-2024-20964
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 · uneditedVulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 8.0.35 and prior and 8.2.0 and prior. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).
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 · high confidenceVulnerability in MySQL Server's security/privileges component (CVE-2024-20964) allows low privileged attackers with network access via multiple protocols to cause a denial of service, resulting in server hang or crash. The vulnerability affects MySQL versions 8.0.35 and prior, and 8.2.0 and prior, and is described as difficult to exploit.
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>= 8.0.0, <= 8.0.35>= 8.1.0, <= 8.2.0CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed MySQL Server versionRun `SELECT VERSION();` from a MySQL client connection, or execute `mysqld --version` from the server command lineAffected if The reported version falls within 8.0.0 through 8.0.35, or within 8.1.0 through 8.2.0 (inclusive)
-
Verify MySQL is listening on network interfacesCheck the MySQL configuration file (my.cnf or my.ini) for the `bind-address` setting, or run `netstat -tlnp | grep 3306` or `ss -tlnp | grep 3306` to see listening addressesAffected if MySQL is bound to 0.0.0.0, a specific non-localhost IP address, or otherwise accessible from the network (not bound to 127.0.0.1 only)
-
Confirm low-privileged user accounts existExecute `SELECT user, host FROM mysql.user WHERE account_locked='N';` to list active user accountsAffected if There are any non-admin, non-root user accounts enabled (the vulnerability targets low privileged attackers)
A user is affected if their MySQL Server version is 8.0.35 or lower, or between 8.1.0 and 8.2.0, and the server is network-accessible with at least one low-privileged user account present.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply the Oracle Critical Patch Update (January 2024 or later) that addresses this vulnerability, or upgrade to a patched MySQL version (8.0.36+ or 8.2.1+). Test thoroughly in staging before production deployment.
MySQL 8.0.36 for 8.0.x users; MySQL 8.2.1 for 8.1.0/8.2.0 users
- 1. Identify your current MySQL Server version using: SELECT VERSION();
- 2. If running MySQL 8.0.x (8.0.0 - 8.0.35), plan upgrade to MySQL 8.0.36
- 3. If running MySQL 8.1.0 or 8.2.0, plan upgrade to MySQL 8.2.1
- 4. Backup all databases before upgrade: mysqldump --all-databases --single-transaction --routines --triggers > full_backup.sql
- 5. Stop the MySQL Server service
- 6. Upgrade MySQL Server packages using your OS package manager (e.g., yum update mysql-server, apt-get install mysql-server, or download from MySQL website)
- 7. Start the MySQL Server service
- 8. Run mysql_upgrade to check and update system tables if needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20964 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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