CVE-2022-44011
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 · uneditedAn issue was discovered in ClickHouse before 22.9.1.2603. An authenticated user (with the ability to load data) could cause a heap buffer overflow and crash the server by inserting a malformed CapnProto object. The fixed versions are 22.9.1.2603, 22.8.2.11, 22.7.4.16, 22.6.6.16, and 22.3.12.19.
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 confidenceAn authenticated user with data loading privileges can trigger a heap buffer overflow by inserting malformed CapnProto objects, causing the ClickHouse server to crash (Denial of Service).
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< 22.3.12.19>= 22.6, < 22.6.6.16>= 22.7, < 22.7.4.16>= 22.8, < 22.8.2.11>= 22.9, < 22.9.1.2603CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 ClickHouse versionRun `clickhouse-server --version` or query `SELECT version()` via clickhouse-clientAffected if The installed version falls within any of these ranges: < 22.3.12.19; >= 22.6, < 22.6.6.16; >= 22.7, < 22.7.4.16; >= 22.8, < 22.8.2.11; >= 22.9, < 22.9.1.2603
-
Verify CapnProto format is availableQuery `SELECT * FROM system.formats WHERE name = 'CapnProto'` to check if the CapnProto input format is registered and enabledAffected if The CapnProto format exists and is listed as available in the system.formats table
-
Check for table functions accepting CapnProtoQuery `SELECT * FROM system.table_functions WHERE name LIKE '%capnproto%'` or check for tables using the CapnProto format in `system.tables`Affected if Any table functions or tables using CapnProto format are present in the system
-
Identify users with data loading privilegesQuery `SELECT name, storage FROM system.users` and check for users with privileges allowing data loading (INSERT or file-like permissions). Also check `system.grants` for data loading rolesAffected if Any user or role has INSERT privileges or the 'loads' permission granted, particularly to remote or file-based sources
You are affected if your ClickHouse version is within the affected ranges AND the CapnProto format is enabled/available AND users with data loading privileges exist in your environment.
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 · scoped22.3.12.1922.6.6.1622.7.4.16
Upgrade ClickHouse to version 22.9.1.2603 or later (or any of the patched versions: 22.8.2.11, 22.7.4.16, 22.6.6.16, 22.3.12.19). If immediate patching is not feasible, restrict or audit the ability to load data from untrusted CapnProto sources.
Upgrade to ClickHouse 22.9.1.2603 or later (or minimum 22.8.2.11, 22.7.4.16, 22.6.6.16, or 22.3.12.19 depending on your release train)
- 1. Identify the current ClickHouse version using 'clickhouse-server --version' or checking the system table.
- 2. Plan for upgrade during a maintenance window - ensure backups are available.
- 3. Stop the ClickHouse server gracefully.
- 4. Upgrade ClickHouse to version 22.9.1.2603 (recommended) or at minimum to one of the fixed versions: 22.8.2.11, 22.7.4.16, 22.6.6.16, or 22.3.12.19.
- 5. Restart the ClickHouse server after upgrade.
- 6. Verify the server starts successfully using 'systemctl status clickhouse-server' or equivalent.
- 7. Validate that CapnProto functionality works correctly with legitimate data.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44011 — 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-2022-44011 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