CVE-2019-16536
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 · uneditedStack overflow leading to DoS can be triggered by a malicious authenticated client in Clickhouse before 19.14.3.3.
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 confidenceA stack overflow vulnerability in ClickHouse versions before 19.14.3.3 allows an authenticated malicious client to trigger a denial of service condition.
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< 19.14.3.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify installed ClickHouse versionRun 'clickhouse-server --version' or 'clickhouse-client --version' to retrieve the exact version number of the ClickHouse server or client installed in your environmentAffected if The version displayed is lower than 19.14.3.3 (for example, 19.14.2, 19.13.x, or any version prefix lower than 19.14.3)
-
Verify ClickHouse service is runningCheck if the ClickHouse server process is active using 'systemctl status clickhouse-server' or 'ps aux | grep clickhouse'Affected if The server is running and the version from step 1 is below 19.14.3.3
-
Confirm authentication is enabledReview the ClickHouse configuration file (typically in /etc/clickhouse-server/config.xml) for user authentication settings, or check if users are defined in users.xmlAffected if Authentication is configured and the server accepts connections from clients - the vulnerability requires an authenticated client to trigger the stack overflow
You are affected if your running ClickHouse version is below 19.14.3.3 AND the server accepts authenticated client connections, as the stack overflow can be triggered by a malicious authenticated user.
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 · scoped19.14.3.3
Upgrade ClickHouse to version 19.14.3.3 or later to remediate this vulnerability.
19.14.3.3 or later
- 1. Backup all ClickHouse data directories and configuration files before proceeding with the upgrade
- 2. Stop the ClickHouse service using systemctl stop clickhouse-server or the equivalent for your setup
- 3. Update the ClickHouse package repository to ensure access to the latest packages
- 4. Install ClickHouse version 19.14.3.3 or later using your package manager (apt-get install clickhouse-server=19.14.3.3 clickhouse-client=19.14.3.3 clickhouse-common=19.14.3.3 or yum install clickhouse-19.14.3.3)
- 5. Verify the installed version matches or exceeds 19.14.3.3 using clickhouse-client --version
- 6. Start the ClickHouse service using systemctl start clickhouse-server
- 7. Test that the service starts successfully and accepts connections
- 8. Verify that authenticated clients can connect normally and the stack overflow vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16536 — 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-2019-16536 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