CVE-2024-20994
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: Information Schema). Supported versions that are affected are 8.0.36 and prior and 8.3.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 confidenceA denial-of-service vulnerability exists in MySQL Server's Information Schema component. Low-privileged attackers with network access can exploit this flaw to cause MySQL Server to hang or experience repeatable crashes, resulting in complete DoS. The vulnerability is rated as difficult to exploit with high attack complexity.
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.36= 8.3.0all versionsall versionsall versionsall versionsCVSS 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.
-
Identify MySQL Server versionRun `mysql --version` from the command line, or connect to MySQL and execute `SELECT VERSION();`Affected if The version returned is 8.0.0 through 8.0.36 inclusive, or exactly 8.3.0, or any 8.3.x version before 8.3.1
-
Confirm Information Schema component is presentConnect to MySQL and execute `USE information_schema; SELECT COUNT(*) FROM tables;` to verify the Information Schema database is accessibleAffected if The query executes successfully, confirming Information Schema is available and functional in the MySQL instance
-
Verify network accessibility of MySQL serviceCheck if MySQL port (default 3306) is listening on a network interface: run `netstat -tlnp | grep 3306` or `ss -tlnp | grep 3306`. Also check firewall rules with `iptables -L -n` or equivalentAffected if MySQL is bound to a non-localhost IP address and is reachable over the network (port 3306 open to external traffic)
-
Identify existing MySQL user accountsConnect to MySQL and execute `SELECT user, host FROM mysql.user;` to list all database usersAffected if There are any user accounts (even low-privilege ones) with network access (host not set to localhost or 127.0.0.1), as these accounts can be used to exploit the vulnerability
You are affected if your MySQL Server version falls within 8.0.0-8.0.36 or is exactly 8.3.0, the Information Schema component is functional, and the database is accessible over the network with any user account.
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 (CPU) that addresses this vulnerability, or upgrade MySQL Server to version 8.0.37 or later (for the 8.0 branch) or 8.3.1 or later (for the 8.3 branch). Network segmentation and restricting database user privileges can further reduce the attack surface.
MySQL 8.0.37+ or 8.3.1+
- 1. Identify the current MySQL Server version by running: SELECT VERSION();
- 2. For MySQL 8.0.x installations: Upgrade to MySQL 8.0.37 or later by following Oracle's upgrade documentation
- 3. For MySQL 8.3.x installations: Upgrade to MySQL 8.3.1 or later
- 4. After upgrade, verify the version with: SELECT VERSION();
- 5. Test application functionality to ensure compatibility with the new MySQL version
- 6. For NetApp products (Active IQ Unified Manager, Oncommand Insight, Oncommand Workflow Automation, Snapcenter): Monitor NetApp security advisories for product-specific patches as these products bundle MySQL Server
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-20994 — 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-20994 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