dbcve.org
Mysql ServerDatabase / datastore · Oracle

CVE-2024-21015

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 8.3.0 or later.
See remediation →
61/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: DML). Supported versions that are affected are 8.0.34 and prior and 8.3.0 and prior. Easily exploitable vulnerability allows high 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 as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/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

Vulnerability in MySQL Server's DML (Data Manipulation Language) component allowing a high-privileged attacker with network access to cause a denial of service (hang or crash) or gain unauthorized insert/update/delete access to some accessible data. The attack does not require user interaction and exploits the DML processing path.

MitigationApply Oracle's Critical Patch Update (April 2024) for MySQL Server, upgrading to version 8.0.35 or later (for 8.0.x branches) or 8.3.1 or later (for 8.3.x). Network access controls and principle of least privilege for database accounts provide defense-in-depth.

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.0.0, <= 8.0.34>= 8.1.0, <= 8.3.0
Active Iq Unified ManagerApplication
Affected:all versions
Oncommand InsightApplication
Affected:all versions
Oncommand Workflow AutomationApplication
Affected:all versions
SnapcenterApplication
Affected:all versions

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
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/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. Check MySQL Server version
    Run 'mysql --version' from command line or execute 'SELECT VERSION();' in a MySQL client session
    Affected if Version is 8.0.0 through 8.0.34, or 8.1.0 through 8.3.0 (check both the major.minor.patch and the full version string)
  2. Verify version parsing
    Confirm the exact version number returned, noting that versions like 8.0.35 and 8.3.1 are NOT in the affected range
    Affected if Version falls within 8.0.0-8.0.34 or 8.1.0-8.3.0 inclusive

If MySQL Server version is 8.0.0-8.0.34 or 8.1.0-8.3.0, the environment is affected by this vulnerability

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.3.0
Interim mitigation

Apply Oracle's Critical Patch Update (April 2024) for MySQL Server, upgrading to version 8.0.35 or later (for 8.0.x branches) or 8.3.1 or later (for 8.3.x). Network access controls and principle of least privilege for database accounts provide defense-in-depth.

Recommended fix High confidence

MySQL Server 8.0.35 or later (8.0.x stable release)

  1. 1. Identify all MySQL Server installations in the environment running versions 8.0.0-8.0.34 or 8.1.0-8.3.0
  2. 2. Schedule a maintenance window for the upgrade procedure
  3. 3. Back up all MySQL databases before proceeding with the upgrade
  4. 4. For MySQL Server installations, upgrade to MySQL Server version 8.0.35 or later (or the latest 8.0.x stable release)
  5. 5. For NetApp products (Active IQ Unified Manager, OnCommand Insight, OnCommand Workflow Automation, Snapcenter), monitor security.netapp.com for available patches and apply them once released
  6. 6. After upgrade, verify MySQL Server starts successfully and application connectivity is restored
  7. 7. Test that the DML operations function normally and the vulnerability is mitigated
Caveat Minor upgrades within 8.0.x typically have low risk, but always test in non-production first; verify application compatibility with the specific 8.0.x version

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

Fix this in Mysql Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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