ClickhouseApplication

CVE-2021-42390

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-14
Fix available
A fix is available. Upgrade to 21.10.2.15 or later.
See remediation →
71/100
Remediation priority · Elevated
Public exploit 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
Divide-by-zero in Clickhouse's DeltaDouble compression codec when parsing a malicious query. The first byte of the compressed buffer is used in a modulo operation without being checked for 0.

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

A detailed technical summary for this CVE is being prepared.

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
ClickhouseApplication
Affected:< 21.10.2.15

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

CVSS:3.1/AV:N/AC:L/PR:L/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 21.10.2.15 or later
Fixed in 21.10.2.15
Recommended fix Moderate confidence

21.10.2.15 or later stable release

  1. Backup your Clickhouse data and configuration files before proceeding with any upgrade
  2. Consult the official Clickhouse upgrade documentation for your installation method (packages, docker, or source build)
  3. For package-based installations: Stop the Clickhouse server service, then update the package repository and install the new version
  4. For docker-based installations: Pull the latest image with a version tag of 21.10.2.15 or later, then recreate the container with the same configuration
  5. For source-based installations: Checkout the tagged release v21.10.2.15 or later and rebuild from source
  6. After upgrade, start the Clickhouse service and verify it runs without errors
  7. Review Clickhouse logs to confirm no division-by-zero errors occur when processing queries using the DeltaDouble compression codec
Caveat Review the Clickhouse release notes between your current version and 21.10.2.15 for any breaking changes in query syntax, functions, or configuration settings that may affect your applications

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,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-42390 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-42390 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