CVE-2024-20962
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: Optimizer). Supported versions that are affected are 8.0.35 and prior and 8.2.0 and prior. Easily exploitable 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 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/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 confidenceA vulnerability in the MySQL Server Optimizer component allows a low-privileged attacker with network access to cause a denial of service through hang or crash conditions. The vulnerability affects MySQL versions 8.0.35 and prior, and 8.2.0 and prior.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Check installed MySQL versionRun 'SELECT VERSION();' or 'mysqld --version' to obtain the server version numberAffected if Version is 8.0.0 through 8.0.35, or 8.1.0 through 8.2.0
-
Verify MySQL network listening statusCheck MySQL configuration files (my.cnf/my.ini) for 'bind-address' settings or run 'SHOW VARIABLES LIKE "bind_address";' to see if MySQL is bound to a network interfaceAffected if MySQL is listening on a non-localhost address (0.0.0.0 or specific IP) and is network-accessible
-
Identify low-privileged database usersRun 'SELECT user, host FROM mysql.user WHERE privileges_level != "YES";' to list non-admin usersAffected if Any low-privileged user accounts exist in the MySQL database
-
Confirm network access to MySQL serviceTest TCP connectivity to the MySQL port (default 3306) from an external host using 'nc -zv <mysql_host> 3306' or telnetAffected if Network connectivity to MySQL port is possible from untrusted networks
Your environment is affected if you run MySQL version 8.0.0-8.0.35 or 8.1.0-8.2.0 with network accessibility and low-privileged user accounts exist.
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 for CVE-2024-20962 when available, or upgrade to a patched MySQL version. Prior to patching, restrict network access to MySQL and limit low-privileged user permissions as a compensating control.
MySQL 8.0.36 or later, or MySQL 8.2.1 or later (preferably latest 8.0.x or 8.2.x stable release)
- 1. Backup all MySQL databases using mysqldump or mysql shell backup utilities
- 2. Review current MySQL 8.0.x or 8.2.x configuration files for compatibility
- 3. Download MySQL 8.0.36 or later (or 8.2.1 or later) from official Oracle MySQL downloads
- 4. Stop the MySQL Server service before upgrading
- 5. Upgrade MySQL Server packages or use MySQL Shell upgrade checker utility
- 6. Start MySQL Server service after upgrade completes
- 7. Run mysql_upgrade to update system tables if prompted
- 8. Verify MySQL Server starts successfully and test application connectivity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20962 — 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-20962 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