CalciteApplication · Apache
CVE-2020-13955
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 · uneditedHttpUtils#getURLConnection method disables explicitly hostname verification for HTTPS connections making clients vulnerable to man-in-the-middle attacks. Calcite uses internally this method to connect with Druid and Splunk so information leakage may happen when using the respective Calcite adapters. The method itself is in a utility class so people may use it to create vulnerable HTTPS connections for other applications. From Apache Calcite 1.26 onwards, the hostname verification will be performed using the default JVM truststore.
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 HttpUtils#getURLConnection method in Apache Calcite explicitly disables hostname verification for HTTPS connections, removing a critical security control and enabling man-in-the-middle attacks. This utility method is used internally by Calcite's Druid and Splunk adapters, potentially causing information leakage over HTTPS connections.
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
CalciteApplication
< 1.26CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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.
-
Identify Apache Calcite installationSearch for calcite JAR files in your classpath, dependencies, or application lib directory. Run: find . -name '*calcite*.jar' 2>/dev/null or check your dependency management (Maven pom.xml, Gradle build.gradle) for org.apache.calcite dependencies.Affected if Apache Calcite is present in the environment and the version is below 1.26
-
Determine installed Calcite versionInspect the calcite JAR filename or check your dependency manifest for the exact version number. If using Maven/Gradle, run: mvn dependency:tree | grep calcite or gradle dependencies | grep calciteAffected if The version is anything less than 1.26 (e.g., 1.25, 1.24, etc.)
-
Check for Druid adapter usageSearch your codebase and configuration for usage of the Druid adapter. Look for adapter configurations referencing 'druid' or classes like org.apache.calcite.adapter.druid.DruidConnectionAffected if The Druid adapter is configured and connects over HTTPS to a Druid broker
-
Check for Splunk adapter usageSearch your codebase and configuration for usage of the Splunk adapter. Look for adapter configurations referencing 'splunk' or classes like org.apache.calcite.adapter.splunk.SplunkConnectionAffected if The Splunk adapter is configured and connects over HTTPS to a Splunk server
-
Verify HTTPS usage with Calcite adaptersReview Calcite adapter connection strings or configuration files. Identify if any Druid or Splunk connections use HTTPS URLs. The vulnerable HttpUtils#getURLConnection method is called when these adapters make HTTPS requests.Affected if Any Druid or Splunk adapter is communicating over HTTPS URLs to external services
You are affected if Apache Calcite version is below 1.26 AND you use the Druid or Splunk adapter with HTTPS connections, because the HttpUtils#getURLConnection method disables hostname verification for those connections.
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.26
Upgrade to Apache Calcite 1.26 or later which implements hostname verification using the default JVM truststore. If upgrading is not possible, avoid using HttpUtils#getURLConnection for HTTPS connections or implement custom hostname verification.
Fix this in Calcite
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13955 — 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-2020-13955 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