dbcve.org
Mysql ServerDatabase / datastore · Oracle

CVE-2024-21176

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to after 8.4.0 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Thread Pooling). Supported versions that are affected are 8.4.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 confidence

A denial-of-service vulnerability exists in MySQL Server's Thread Pooling component. Low-privileged attackers with network access via multiple protocols can exploit this flaw to cause MySQL Server to hang or repeatedly crash, resulting in complete availability loss.

MitigationApply the Oracle Critical Patch Update (CPU) containing the fix for CVE-2024-21176, upgrading MySQL Server to a patched version beyond 8.4.0. Schedule maintenance window for patch deployment and test in non-production environment first.

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
Mysql ServerDatabase / datastore
Affected:<= 8.4.0

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
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 checks

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

  1. Confirm MySQL Server installation and version
    Run 'mysql --version' or 'SELECT VERSION();' to obtain the installed MySQL Server version
    Affected if Version is 8.4.0 or lower (8.4.0, 8.3.x, 8.2.x, 8.1.x, 8.0.x, etc.)
  2. Check if Thread Pooling is enabled
    Execute query: SHOW VARIABLES LIKE 'thread_pool%'; to see thread pool related configuration
    Affected if Thread pool is enabled (thread_pool_size is set to a non-default value or thread_pool_mode is configured)
  3. Verify network accessibility
    Check MySQL listener ports (default 3306) with 'netstat -tlnp | grep mysql' or review firewall rules
    Affected if MySQL is reachable over network (bind-address is not 127.0.0.1 or firewall allows external connections)
  4. Check current user privileges
    Run 'SELECT user, host FROM mysql.user;' to enumerate low-privileged accounts
    Affected if Low-privileged network-accessible accounts exist in MySQL (users without SUPER or admin privileges)

You are affected if MySQL Server version is 8.4.0 or lower AND Thread Pooling is enabled AND the server is network-accessible to low-privileged users.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 8.4.0
Interim mitigation

Apply the Oracle Critical Patch Update (CPU) containing the fix for CVE-2024-21176, upgrading MySQL Server to a patched version beyond 8.4.0. Schedule maintenance window for patch deployment and test in non-production environment first.

Recommended fix High confidence

MySQL 8.4.1 or later (or 8.0.37+ if remaining on 8.0 branch)

  1. 1. Review Oracle Critical Patch Update advisory for April 2024 to confirm fixed version details
  2. 2. Backup all MySQL databases before upgrading
  3. 3. Stop the MySQL Server service
  4. 4. Upgrade MySQL Server to version 8.4.1 or later (the first release after 8.4.0 that includes the security fix)
  5. 5. Verify the upgrade by checking the MySQL version: SELECT VERSION();
  6. 6. Test application functionality to ensure compatibility
  7. 7. Restart the MySQL Server service
Caveat Review MySQL 8.4 release notes for any behavioral changes between 8.4.0 and 8.4.1; minor point releases typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mysql Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21176 — 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-2024-21176 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