dbcve.org
MariaDBDatabase / datastore

CVE-2022-24048

HIGH · 7.8 CVSS v3.1 Published 2022-02-18
Fix available
A fix is available. Upgrade to 10.2.42 / 10.3.33 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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
MariaDB CONNECT Storage Engine Stack-based Buffer Overflow Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of MariaDB. Authentication is required to exploit this vulnerability. The specific flaw exists within the processing of SQL queries. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of the service account. Was ZDI-CAN-16191.

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
How this class of weakness works · CWE-121

Data overflows a fixed-size buffer allocated on the stack, overwriting adjacent stack memory — including saved return addresses — which is the classic route to redirecting execution into attacker-supplied code. Crafted input is all it takes. Remediation is strict length checks, safe bounded string and memory functions, and modern stack-protection mitigations.

General guidance for the stack-based buffer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
MariaDBDatabase / datastore
Affected:>= 10.2.0, < 10.2.42>= 10.3.0, < 10.3.33>= 10.4.0, < 10.4.23>= 10.5.0, < 10.5.14>= 10.6.0, < 10.6.6>= 10.7.0, < 10.7.2= 10.8.0
FedoraOperating system
Affected:= 34= 35= 36

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 10.2.42 / 10.3.33 / 10.4.23 or later
Fixed in 10.2.4210.3.3310.4.23
Vendor patch mariadb.com →
Recommended fix High confidence

MariaDB 10.2.42, 10.3.33, 10.4.23, or 10.5.14 (or later stable release in your branch)

  1. 1. Identify current MariaDB version by running: `mysql --version` or `mariadb --version`
  2. 2. Stop the MariaDB service: `systemctl stop mariadb` or `systemctl stop mysql`
  3. 3. Create a backup of all databases: `mysqldump --all-databases --single-transaction > backup.sql` (or use `mariabackup` for large databases)
  4. 4. For RHEL/CentOS/Fedora: Run `sudo dnf update mariadb` or `sudo dnf update mariadb-server` to install the fixed packages
  5. 5. For Debian/Ubuntu: Use the appropriate package manager or MariaDB repository to upgrade to the fixed version
  6. 6. After upgrade, start the MariaDB service: `systemctl start mariadb` or `systemctl start mysql`
  7. 7. Verify the version is now >= 10.2.42, 10.3.33, 10.4.23, or 10.5.14: `mysql --version`
  8. 8. Test that applications can connect and function correctly
Caveat Standard database upgrade risk: test in staging first; ensure backups are verified before production upgrade

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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