Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2021-36749 β€” AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Apache Druid allows authenticated users to read local files via HTTP InputSource. πŸ’₯ **Consequences**: Arbitrary file read (e.g., /etc/passwd), data leakage, potential server compromise.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: The **HTTP InputSource** in the ingestion system is misconfigured. It allows reading from unintended sources (like local file system) instead of just remote HTTP sources.…

Q3Who is affected? (Versions/Components)

🏒 **Vendor**: Apache Software Foundation. πŸ“¦ **Product**: Apache Druid. πŸ“… **Affected Versions**: Version **<= 0.21.1**. πŸ—“οΈ **Published**: 2021-09-24.

Q4What can hackers do? (Privileges/Data)

πŸ•΅οΈ **Action**: Hackers can read **any file** accessible by the Druid server process. πŸ“‚ **Data**: Local filesystem data (e.g., /etc/passwd, config files).…

Q5Is exploitation threshold high? (Auth/Config)

πŸ”‘ **Threshold**: **Medium**. Requires **Authentication**. βš™οΈ **Config**: Users must be able to specify the **HTTP InputSource** in the ingestion task. Not direct privilege escalation, but indirect via app interaction.

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ’£ **Exploit**: **Yes**, public PoCs exist. πŸ“‚ **GitHub**: Multiple repos (e.g., BrucessKING, Jun-5heng) provide curl commands and Python scripts. 🌐 **Wild Exploitation**: Likely, given simple curl-based PoCs.

Q7How to self-check? (Features/Scanning)

πŸ” **Check**: Scan for Apache Druid on port **8888**. πŸ§ͺ **Test**: Send POST request to `/druid/indexer/v1/sampler?for=connect` with HTTP InputSource pointing to `file:///etc/passwd`.…

Q8Is it fixed officially? (Patch/Mitigation)

πŸ› οΈ **Fix**: Upgrade to version **> 0.21.1**. πŸ“’ **Official**: Apache announced the fix in mailing lists (CVE-2021-36749). πŸ”„ **Status**: Incomplete fix of previous CVE, so patch is critical.

Q9What if no patch? (Workaround)

🚧 **Workaround**: If no patch, **restrict network access** to Druid ingestion endpoints. πŸ”’ **Auth**: Ensure strong authentication and limit who can submit ingestion tasks.…

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Urgency**: **High**. πŸ“‰ **Risk**: Data leakage is severe. πŸš€ **Priority**: Patch immediately if running <= 0.21.1. πŸ“’ **Alert**: Public exploits make this easy to weaponize. Don't ignore!