dbcve.org
DruidApplication · Apache

CVE-2020-1958

MEDIUM · 6.5 CVSS v3.1 Published 2020-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
When LDAP authentication is enabled in Apache Druid 0.17.0, callers of Druid APIs with a valid set of LDAP credentials can bypass the credentialsValidator.userSearch filter barrier that determines if a valid LDAP user is allowed to authenticate with Druid. They are still subject to role-based authorization checks, if configured. Callers of Druid APIs can also retrieve any LDAP attribute values of users that exist on the LDAP server, so long as that information is visible to the Druid server. This information disclosure does not require the caller itself to be a valid LDAP user.

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 Druid 0.17.0 with LDAP authentication enabled has an authentication bypass vulnerability where callers with valid LDAP credentials can bypass the credentialsValidator.userSearch filter barrier that determines if a valid LDAP user is allowed to authenticate. Additionally, unauthenticated or authenticated callers can retrieve LDAP attribute values of any user visible to the Druid server.

MitigationUpgrade Apache Druid to a version that addresses this vulnerability. If immediate upgrade is not possible, review and restrict LDAP userSearch configuration and ensure role-based authorization is properly configured.

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
DruidApplication
Affected:= 0.17.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify Apache Druid version
    Check the Druid version by reviewing the release documentation, startup logs, or by querying the Druid console/API version endpoint. Common locations include the Druid console footer or the /status endpoint.
    Affected if The installed version is exactly 0.17.0
  2. Verify LDAP authentication is enabled
    Review the Druid configuration files (typically in the configuration directory) for LDAP-related settings. Look for authenticationChain configurations containing LDAP authenticator definitions.
    Affected if LDAP authentication is configured and enabled in the Druid authentication chain
  3. Inspect LDAP userSearch configuration
    Examine the Druid LDAP authenticator configuration for the userSearch base and filter settings. This is typically defined under credentialsValidator.userSearch in the authentication configuration.
    Affected if The credentialsValidator.userSearch filter is configured, indicating the vulnerable filter barrier is in place
  4. Check Druid console/API network exposure
    Determine if the Druid console and API endpoints are accessible from untrusted networks. Review network firewall rules and Druid server binding configuration.
    Affected if The Druid console or API is accessible from network locations beyond trusted administrators

A user is affected if running Apache Druid version 0.17.0 with LDAP authentication enabled and the credentialsValidator.userSearch filter is configured, regardless of network exposure due to the attribute retrieval aspect of the flaw.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache Druid to a version that addresses this vulnerability. If immediate upgrade is not possible, review and restrict LDAP userSearch configuration and ensure role-based authorization is properly configured.

Fix this in Druid Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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