CVE-2018-14669
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 · uneditedClickHouse MySQL client before versions 1.1.54390 had "LOAD DATA LOCAL INFILE" functionality enabled that allowed a malicious MySQL database read arbitrary files from the connected ClickHouse server.
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 confidenceThe ClickHouse MySQL client before version 1.1.54390 had LOAD DATA LOCAL INFILE functionality enabled, allowing a malicious MySQL server to trick the client into reading arbitrary files from the ClickHouse server and transmitting them to the attacker.
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< 1.1.54390CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Determine installed ClickHouse versionRun `clickhouse-client --version` or execute `SELECT version()` query in ClickHouseAffected if The version number is lower than 1.1.54390
-
Identify MySQL client usage in ClickHouseCheck if any MySQL database engine or table function is configured by querying system tables such as `system.tables` or `system.databases` for mysql engine references, or review ClickHouse configuration files for MySQL-compatible connection settingsAffected if MySQL protocol client or MySQL database engine is actively configured or in use
-
Inspect MySQL client configuration for LOCAL INFILEReview ClickHouse MySQL connection settings and configuration for the presence of the `allow_local_infile` setting or similar MySQL client options; check if LOAD DATA statements are being executed against MySQL data sourcesAffected if LOAD DATA LOCAL INFILE is explicitly allowed or the MySQL client is configured with default permissions that permit local file reads via the LOCAL INFILE option
You are affected if your ClickHouse version is below 1.1.54390 AND you use the MySQL client functionality with LOAD DATA LOCAL INFILE enabled, allowing a malicious MySQL server to read files from your server.
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.
From vendor data1.1.54390
Upgrade ClickHouse to version 1.1.54390 or later where this functionality is disabled by default, or explicitly disable LOAD DATA LOCAL INFILE in the MySQL client configuration.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14669 — 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-14669 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