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**: Mammoth (Word-to-HTML tool) has a critical flaw in handling `.docx` files. <br>💥 **Consequences**: Attackers can trigger **Directory Traversal** (CWE-22) or cause **Resource Exhaustion** (DoS).…
🛡️ **Root Cause**: **Missing Input Validation**. Specifically, the tool fails to verify file paths or types when processing documents. <br>🔍 **CWE**: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory).
Q3Who is affected? (Versions/Components)
📦 **Affected Versions**: <br>• `mammoth` **0.3.25** <br>• All versions **before 1.11.0** <br>👤 **Developer**: Michael Williamson (Personal Project).
Q4What can hackers do? (Privileges/Data)
🕵️ **Attacker Capabilities**: <br>• **Read**: Access sensitive files outside the intended directory via traversal. <br>• **Disrupt**: Crash the service via resource overconsumption.…
📢 **Public Exploit**: **No**. The `pocs` field is empty. <br>🔗 **References**: Proof-of-concept links exist on GitHub/Snyk, but no automated wild exploitation tools are confirmed in the data.
Q7How to self-check? (Features/Scanning)
🔍 **Self-Check**: <br>1. Scan your dependency tree for `mammoth` version < 1.11.0. <br>2. Check if your app processes untrusted `.docx` files using this library. <br>3. Look for file path manipulation in logs.
Q8Is it fixed officially? (Patch/Mitigation)
🩹 **Fix Status**: **Yes**. <br>• **Patch**: Upgrade to version **1.11.0** or later. <br>• **Commit**: Fix confirmed in `c54aaeb` on GitHub.
Q9What if no patch? (Workaround)
🚧 **No Patch Workaround**: <br>• **Sanitize Inputs**: Validate all file paths and extensions strictly before passing to Mammoth.…