dbcve.org
ClickhouseApplication

CVE-2018-14670

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-15
Fix available
A fix is available. Upgrade to 1.1.54131 or later.
See remediation →
100/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
Incorrect configuration in deb package in ClickHouse before 1.1.54131 could lead to unauthorized use of the database.

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

An incorrect configuration in the ClickHouse deb package prior to version 1.1.54131 creates an access control weakness that could allow unauthorized users to access the database. The specific misconfiguration in the packaged default settings enables bypass of intended authentication or authorization controls.

MitigationUpgrade ClickHouse to version 1.1.54131 or later and review database user permissions and configuration files for any unauthorized changes.

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:< 1.1.54131

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 installed ClickHouse version
    Run 'clickhouse-server --version' or 'dpkg -l clickhouse-server' to determine the installed version number
    Affected if Version is below 1.1.54131
  2. Locate ClickHouse configuration directory
    Check for the presence of /etc/clickhouse-server/ directory which contains the deb package default configuration files
    Affected if The deb package configuration directory exists (indicating this install method was used)
  3. Examine config.xml for access control settings
    Inspect /etc/clickhouse-server/config.xml for <listen_host>, <listen_port>, or network binding settings that may allow unauthenticated access
    Affected if Network interfaces are bound to 0.0.0.0 or unrestricted addresses without proper access controls configured
  4. Review users.xml for authentication configuration
    Examine /etc/clickhouse-server/users.xml to verify user accounts and authentication settings are properly configured
    Affected if Default users exist with weak or missing passwords, or authentication is disabled for any user

Environment is affected if ClickHouse version is below 1.1.54131 AND the deb package default configuration files contain permissive network access settings or weak authentication configuration.

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 1.1.54131 or later
Fixed in 1.1.54131
Interim mitigation

Upgrade ClickHouse to version 1.1.54131 or later and review database user permissions and configuration files for any unauthorized changes.

Recommended fix Moderate confidence

ClickHouse 1.1.54131 or later (ideally latest stable 1.1.x release)

  1. Check current ClickHouse version: systemctl status clickhouse-server or clickhouse-client --version
  2. Stop ClickHouse service: sudo systemctl stop clickhouse-server
  3. Update the ClickHouse repository: sudo apt-get update
  4. Install the fixed version: sudo apt-get install clickhouse-server clickhouse-client
  5. Start ClickHouse service: sudo systemctl start clickhouse-server
  6. Verify the version after upgrade: clickhouse-client --version
  7. Ensure proper authorization configuration exists in /etc/clickhouse-server/config.xml, particularly check for proper bind_address and authentication settings
Caveat Review release notes for 1.1.54131+ to check for any breaking changes in your specific use case; consider testing in staging first

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

Fix this in Clickhouse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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