CVE-2018-14671
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 · uneditedIn ClickHouse before 18.10.3, unixODBC allowed loading arbitrary shared objects from the file system which led to a Remote Code Execution vulnerability.
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 confidenceIn ClickHouse before version 18.10.3, the unixODBC integration allows loading arbitrary shared objects (.so files) from the file system, enabling an attacker to execute arbitrary code by specifying a malicious library path.
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< 18.10.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed ClickHouse versionRun `clickhouse-server --version` or `clickhouse-client --version` to determine the exact version numberAffected if The version is lower than 18.10.3 (e.g., 18.10.2, 18.6.0, etc.)
-
Verify unixODBC integration is presentCheck if the unixODBC driver manager is installed on the system (e.g., `odbcinst -q -d` or look for libodbc.so in the system)Affected if unixODBC is installed and ClickHouse was built with ODBC support
-
Identify if ClickHouse has ODBC function support enabledCheck ClickHouse configuration files (typically in /etc/clickhouse-server/) for ODBC function definitions or check if the clickhouse-odbc-bridge process existsAffected if ODBC table functions (odbc()) are enabled in the configuration or accessible to users
-
Check for ODBC driver configuration filesInspect /etc/odbc.ini or /etc/unixODBC/odbc.ini for data source definitions that ClickHouse might useAffected if ODBC data sources are configured and accessible to the ClickHouse process
A user is affected if they run ClickHouse version below 18.10.3 AND have unixODBC integration enabled, allowing potential loading of malicious shared libraries through ODBC function calls.
Generated from the published advisory. Verify against your own configuration.
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 · scoped18.10.3
Upgrade ClickHouse to version 18.10.3 or later; if unixODBC is not required, disable or remove the unixODBC integration to eliminate the attack surface.
18.10.3 or later
- Backup your ClickHouse data and configuration files before upgrading
- Stop the ClickHouse server service
- Upgrade ClickHouse to version 18.10.3 or later using your package manager or installation method
- Verify the upgrade was successful by checking the ClickHouse version
- Restart the ClickHouse server service
- Test that your applications can connect and query the database properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14671 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-14671 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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