dbcve.org
MariaDBDatabase / datastore

CVE-2022-27448

HIGH · 7.5 CVSS v3.1 Published 2022-04-14
Fix available
A fix is available. Upgrade to 10.3.35 / 10.4.25 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges 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
There is an Assertion failure in MariaDB Server v10.9 and below via 'node->pcur->rel_pos == BTR_PCUR_ON' at /row/row0mysql.cc.

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

Attacker-controllable input can reach an assertion that aborts the process when it fails, so a check meant for debugging becomes a denial-of-service in production. A single crafted request takes the service down. The fix is to handle unexpected input gracefully on reachable paths rather than asserting on it.

General guidance for the reachable assertion 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.3.0, < 10.3.35>= 10.4.0, < 10.4.25>= 10.5.0, < 10.5.16>= 10.6.0, < 10.6.8>= 10.7.0, < 10.7.4
Debian LinuxOperating system
Affected:= 10.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.3.35 / 10.4.25 / 10.5.16 or later
Fixed in 10.3.3510.4.2510.5.16
Vendor patch jira.mariadb.org →
Recommended fix High confidence

MariaDB 10.3.35, 10.4.25, 10.5.16, or 10.6.8 (depending on your current branch)

  1. 1. Identify the current MariaDB version by running 'mysql --version' or 'SELECT VERSION();'
  2. 2. Determine which version branch you are on (10.3.x, 10.4.x, 10.5.x, or 10.6.x)
  3. 3. Back up all databases before upgrading using 'mysqldump --all-databases > backup.sql'
  4. 4. For MariaDB 10.3.x: upgrade to version 10.3.35 or later
  5. 5. For MariaDB 10.4.x: upgrade to version 10.4.25 or later
  6. 6. For MariaDB 10.5.x: upgrade to version 10.5.16 or later
  7. 7. For MariaDB 10.6.x: upgrade to version 10.6.8 or later
  8. 8. Use your system's package manager (apt, yum, dnf) or MariaDB's official repositories to perform the upgrade
Caveat Upgrades within same major.minor branch are generally safe but test thoroughly; review MariaDB upgrade notes for any configuration changes required

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-27448 — 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-27448 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