SSRF in lobehub/lobe-chat with native web fetch module
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| lobehub | lobe-chat | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Lobehub | Lobe Chat | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-fgx4-p8xf-qhp9 | Lobe Chat vulnerable to Server-Side Request Forgery with native web fetch module |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.322% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lobehub
Lobehub lobe Chat |
|
| Vendors & Products |
Lobehub
Lobehub lobe Chat |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | LobeChat is an open source chat application platform. The web-crawler package in LobeChat version 1.136.1 allows server-side request forgery (SSRF) in the tools.search.crawlPages tRPC endpoint. A client can supply an arbitrary urls array together with impls containing the value naive. The service passes the user URLs to Crawler.crawl and the naive implementation performs a server-side fetch of each supplied URL without validating or restricting internal network addresses (such as localhost, 127.0.0.1, private IP ranges, or cloud instance metadata endpoints). This allows an attacker with a valid user token (or in development mode using a bypass header) to make the server disclose responses from internal HTTP services, potentially exposing internal API data or cloud metadata credentials. Version 1.136.2 fixes the issue. Update to version 1.136.2. No known workarounds exist. | |
| Title | SSRF in lobehub/lobe-chat with native web fetch module | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|