This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login.
Read the full analysis →
Q1What is this vulnerability? (Essence + Consequences)
🚨 **Essence**: `eslint-ban-moment` v3.0.0 & prior leaks sensitive **Supabase URI** in `.env`. 💥 **Consequences**: Data leakage, modification, or deletion. Critical integrity/availability loss.
Q2Root Cause? (CWE/Flaw)
🛡️ **Root Cause**: **CWE-260** (Password in Plain Text). Sensitive credentials exposed in configuration files (`.env`).
Q3Who is affected? (Versions/Components)
👥 **Affected**: `eslint-ban-moment` by **kristoferfannar**. Versions **3.0.0 and earlier**. Personal developer project.
Q4What can hackers do? (Privileges/Data)
🕵️ **Attacker Actions**: Full access to Supabase. Can **read**, **modify**, or **delete** data. High impact on Confidentiality, Integrity, and Availability.
Q5Is exploitation threshold high? (Auth/Config)
⚡ **Exploitation**: **Low Threshold**. CVSS: **AV:N/AC:L/PR:N/UI:N**. No auth needed. No user interaction. Network accessible.
Q6Is there a public Exp? (PoC/Wild Exploitation)
💣 **Public Exploit**: **No**. `pocs` list is empty. No known wild exploitation yet. But risk is high due to ease.
Q7How to self-check? (Features/Scanning)
🔍 **Self-Check**: Scan for `.env` files in project root. Look for **Supabase URI** or API keys. Use secret scanning tools.
Q8Is it fixed officially? (Patch/Mitigation)
✅ **Fixed**: **Yes**. Patch available via GitHub commit. Check **GHSA-2486-4cjg-pw98** for official advisory.
Q9What if no patch? (Workaround)
🚧 **No Patch?**: **Rotate** Supabase keys immediately. Remove `.env` from version control. Use environment variables securely.
Q10Is it urgent? (Priority Suggestion)
🔥 **Urgency**: **CRITICAL**. CVSS Score is **High** (H/H/H). Fix immediately to prevent data breach. Priority: **P0**.