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**: FastGPT exposes an unauthenticated HTTP proxy endpoint (`/api/core/app/httpTools/runTool`). π₯ **Consequences**: Attackers can abuse this to perform Server-Side HTTP Request Forgery (SSRF).β¦
π‘οΈ **CWE-306**: Missing Authentication for Critical Function. π **Flaw**: The HTTP tool testing endpoint lacks any identity verification. It acts as a full HTTP proxy without checking who is asking.
π΅οΈ **Privileges**: No authentication required (PR:N). Any internet user can exploit it. πΎ **Data**: High impact on Confidentiality (C:H) and Integrity (I:H).β¦
π **Threshold**: LOW. π **Auth**: None required. βοΈ **Config**: Network accessible (AV:N). If the service is exposed to the internet, exploitation is trivial.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π **Public Exp?**: No specific PoC code provided in the data. π **Wild Exp**: High risk due to CVSS Vector `AV:N` (Network) and `PR:N` (No Privileges).β¦
π **Self-Check**: Scan for the endpoint `/api/core/app/httpTools/runTool`. π§ͺ **Test**: Send a request to this URL without any API keys or tokens. If it returns a 200 OK or proxy response, you are vulnerable.
Q8Is it fixed officially? (Patch/Mitigation)
β **Fixed**: Yes. π οΈ **Patch**: Upgrade to **FastGPT v4.14.9.5** or later. π **Ref**: See GitHub Advisory GHSA-w36r-f268-pwrj and PR #6640.
Q9What if no patch? (Workaround)
π§ **Workaround**: If you cannot upgrade immediately: 1. **Block Access**: Use a WAF or Nginx config to deny external access to `/api/core/app/httpTools/runTool`. 2.β¦
π₯ **Urgency**: HIGH. π **Priority**: Patch immediately. βοΈ **Reason**: CVSS Score is high (likely 9.0+ based on vector), affects critical infrastructure (LLM knowledge base), and requires no authentication.β¦