dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2024-6873

HIGH · 8.1 CVSS v3.1 Published 2024-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
It is possible to crash or redirect the execution flow of the ClickHouse server process from an unauthenticated vector by sending a specially crafted request to the ClickHouse server native interface. This redirection is limited to what is available within a 256-byte range of memory at the time of execution, and no known remote code execution (RCE) code has been produced or exploited.  Fixes have been merged to all currently supported version of ClickHouse. If you are maintaining your own forked version of ClickHouse or using an older version and cannot upgrade, the fix for this vulnerability can be found in this commit  https://github.com/ClickHouse/ClickHouse/pull/64024 .

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 · moderate confidence

ClickHouse server contains a vulnerability in its native protocol interface that allows unauthenticated attackers to crash the server or redirect execution flow within a limited 256-byte memory range by sending specially crafted requests. No remote code execution has been demonstrated.

MitigationUpgrade ClickHouse to a version containing the fix (all currently supported versions), or for forked/older versions, apply the fix from commit PR #64024.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/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. Confirm ClickHouse server is running
    Run 'ps aux | grep clickhouse' or check if port 9000 (default native protocol port) is listening with 'netstat -tlnp | grep 9000'
    Affected if ClickHouse is running and accepting native protocol connections on port 9000
  2. Identify installed ClickHouse version
    Run 'clickhouse-client --version' or 'clickhouse-server --version', or query 'SELECT version()' via any client connection
    Affected if The installed version is older than the fixed release and matches the affected version range
  3. Verify native protocol interface is exposed
    Check if port 9000 (default native protocol) is bound and accessible with 'nc -zv localhost 9000' or review ClickHouse config.xml for '<port>9000</port>' under the protocol section
    Affected if The native protocol port 9000 is open and accepting connections
  4. Check for unauthenticated native protocol access
    Attempt a basic native protocol connection using 'clickhouse-client --host <target> --port 9000' without credentials to verify the interface accepts unauthenticated requests
    Affected if The native protocol accepts connections without authentication

You are affected if ClickHouse is running with the native protocol enabled (port 9000) and the installed version falls within the vulnerable range prior to the PR #64024 fix.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ClickHouse to a version containing the fix (all currently supported versions), or for forked/older versions, apply the fix from commit PR #64024.

Recommended fix Moderate confidence

Latest supported ClickHouse release (contact ClickHouse for current supported versions)

  1. Upgrade to the latest supported release of ClickHouse server to obtain the vulnerability fix
  2. If using a forked version or older unsupported release, apply the fix from GitHub PR #64024: https://github.com/ClickHouse/ClickHouse/pull/64024
  3. After upgrading, verify the ClickHouse server native interface is not exposed to untrusted networks if possible

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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