Loading vulnerability…
In Apache Druid 0.17.0, when LDAP authentication is enabled, the credentialsValidator.userSearch filter barrier can be bypassed by callers with valid LDAP credentials. This allows unauthorized users to authenticate with Druid APIs, bypassing intended user search restrictions. Additionally, Druid APIs can be used to retrieve any LDAP attribute values for users present on the LDAP server, exposing sensitive directory information even to unauthenticated callers, provided the Druid server can access that information.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2020-1958, an LDAP injection vulnerability in Apache Druid 0.17.0. The main exploit is implemented in 'poc.py', a Python script that targets the Druid API endpoint (typically http://127.0.0.1:8888/) and abuses the authentication mechanism to enumerate LDAP users and exfiltrate arbitrary LDAP attribute values. The exploit works by crafting malicious usernames that manipulate the LDAP search filter, allowing the attacker to bypass intended access controls. The repository includes a README with detailed setup instructions for a vulnerable Druid instance and an OpenLDAP server, as well as a sample 'users.ldif' file for populating the LDAP directory. The attack vector is network-based, requiring access to the Druid API. The exploit does not require valid credentials and demonstrates information disclosure by extracting sensitive user data from the LDAP server.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.