dbcve.org
Apache Calcite AvaticaWeb server / proxy · Apache

CVE-2022-36364

HIGH · 8.8 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 1.22.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Apache Calcite Avatica JDBC driver creates HTTP client instances based on class names provided via `httpclient_impl` connection property; however, the driver does not verify if the class implements the expected interface before instantiating it, which can lead to code execution loaded via arbitrary classes and in rare cases remote code execution. To exploit the vulnerability: 1) the attacker needs to have privileges to control JDBC connection parameters; 2) and there should be a vulnerable class (constructor with URL parameter and ability to execute code) in the classpath. From Apache Calcite Avatica 1.22.0 onwards, it will be verified that the class implements the expected interface before invoking its constructor.

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 confidence

Apache Calcite Avatica JDBC driver instantiates HTTP client classes based on the `httpclient_impl` connection property without verifying the class implements the expected interface, allowing arbitrary code execution if an attacker controls connection parameters and a vulnerable class exists in the classpath.

MitigationUpgrade to Apache Calcite Avatica 1.22.0 or later which adds interface verification before class instantiation. If upgrading is not possible, restrict who can control JDBC connection parameters and ensure no vulnerable classes are in the classpath.

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
Apache Calcite AvaticaWeb server / proxy
Affected:< 1.22.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Calcite Avatica JDBC driver in use
    Search for calcite-avatica or calcite-avatica-core JAR files in your application classpath, dependencies, or lib directories. Check pom.xml, build.gradle, or similar dependency management files for these artifacts.
    Affected if The Calcite Avatica JDBC driver is present in your environment and its version is below 1.22.0
  2. Determine the installed version of Calcite Avatica
    Examine the JAR file name or check the manifest file (META-INF/MANIFEST.MF) inside the calcite-avatica or calcite-avatica-core JAR for the Implementation-Version attribute. Alternatively, query the driver at runtime via Driver.getVersion() or inspect your dependency lock file.
    Affected if The discovered version is any version prior to 1.22.0 (e.g., 1.21.0, 1.20.0, etc.)
  3. Check for httpclient_impl connection property usage
    Search your codebase, configuration files, connection string definitions, and logs for occurrences of the string 'httpclient_impl' in JDBC connection parameters or URL properties.
    Affected if The httpclient_impl property is used in any JDBC connection configuration within your application
  4. Inspect classpath for custom HTTP client implementations
    Examine all JAR files and classes in your runtime classpath for classes that could be specified as the httpclient_impl value. Look for any custom HTTP client classes not part of the standard Apache HttpClient library, particularly those with constructors that could execute arbitrary code when instantiated.
    Affected if Custom or third-party HTTP client classes exist in the classpath that could be loaded via the httpclient_impl property

You are affected if your environment uses Apache Calcite Avatica with a version below 1.22.0, the httpclient_impl connection property is accessible to untrusted input, and potentially exploitable HTTP client classes exist in your classpath.

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.22.0 or later
Fixed in 1.22.0
Interim mitigation

Upgrade to Apache Calcite Avatica 1.22.0 or later which adds interface verification before class instantiation. If upgrading is not possible, restrict who can control JDBC connection parameters and ensure no vulnerable classes are in the classpath.

Recommended fix High confidence

Apache Calcite Avatica 1.22.0 or later

  1. Upgrade Apache Calcite Avatica dependency to version 1.22.0 or later
  2. Update the version in your build configuration (Maven pom.xml, Gradle build.gradle, or dependency management system)
  3. Verify the upgrade was successful by checking the resolved library version
  4. Conduct regression testing to ensure application functionality remains intact

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

Fix this in Apache Calcite Avatica Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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