dbcve.org
ClickhouseApplication

CVE-2022-44010

HIGH · 7.5 CVSS v3.1 Published 2023-11-23
Fix available
A fix is available. Upgrade to 22.3.12.19 / 22.6.6.16 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An issue was discovered in ClickHouse before 22.9.1.2603. An attacker could send a crafted HTTP request to the HTTP Endpoint (usually listening on port 8123 by default), causing a heap-based buffer overflow that crashes the process. This does not require authentication. The fixed versions are 22.9.1.2603, 22.8.2.11, 22.7.4.16, 22.6.6.16, and 22.3.12.19.

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

A heap-based buffer overflow vulnerability in ClickHouse's HTTP endpoint (port 8123) allows unauthenticated remote attackers to crash the server by sending specially crafted HTTP requests. The vulnerability affects versions prior to 22.9.1.2603 and multiple interim releases.

MitigationUpgrade ClickHouse to one of the fixed versions (22.9.1.2603, 22.8.2.11, 22.7.4.16, 22.6.6.16, or 22.3.12.19). If immediate upgrading is not feasible, consider restricting network access to port 8123 or disabling the HTTP endpoint if not required.

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
ClickhouseApplication
Affected:< 22.3.12.19>= 22.6, < 22.6.6.16>= 22.7, < 22.7.4.16>= 22.8, < 22.8.2.11>= 22.9, < 22.9.1.2603

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

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 if ClickHouse HTTP endpoint is listening on port 8123
    Run 'netstat -tlnp | grep 8123' or 'ss -tlnp | grep 8123' to see if the HTTP server is bound to port 8123
    Affected if Port 8123 is listening and accessible over the network - the vulnerability requires the HTTP endpoint to be enabled and reachable
  2. Identify installed ClickHouse version
    Run 'clickhouse-server --version' or query 'SELECT version()' via the HTTP interface on port 8123
    Affected if The installed version number is returned and must be compared against the affected ranges
  3. Compare version against affected ranges
    Check if the installed version falls into any of these ranges: < 22.3.12.19; >= 22.6 to < 22.6.6.16; >= 22.7 to < 22.7.4.16; >= 22.8 to < 22.8.2.11; >= 22.9 to < 22.9.1.2603
    Affected if The installed version matches any of these ranges - the environment is vulnerable to remote denial-of-service via heap overflow on the HTTP endpoint

If port 8123 is exposed and the ClickHouse version falls within any of the affected version ranges, the environment is vulnerable to CVE-2022-44010.

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 22.3.12.19 / 22.6.6.16 / 22.7.4.16 or later
Fixed in 22.3.12.1922.6.6.1622.7.4.16
Interim mitigation

Upgrade ClickHouse to one of the fixed versions (22.9.1.2603, 22.8.2.11, 22.7.4.16, 22.6.6.16, or 22.3.12.19). If immediate upgrading is not feasible, consider restricting network access to port 8123 or disabling the HTTP endpoint if not required.

Recommended fix High confidence

22.9.1.2603 (or any of: 22.8.2.11, 22.7.4.16, 22.6.6.16, 22.3.12.19)

  1. 1. Backup your ClickHouse data and configuration files before upgrading.
  2. 2. Stop the ClickHouse server service.
  3. 3. Update ClickHouse to a fixed version: 22.9.1.2603 (recommended latest), or at minimum one of 22.8.2.11, 22.7.4.16, 22.6.6.16, or 22.3.12.19 depending on your current branch.
  4. 4. Verify the upgrade by checking the ClickHouse version: SELECT version();
  5. 5. Restart the ClickHouse server service.
  6. 6. Test that the HTTP endpoint (port 8123) responds correctly and the server is operational.
Caveat Standard minor version upgrade precautions apply - test in staging first; review release notes for any behavior changes in your version path

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

Fix this in Clickhouse Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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