Refly through 1.1.0 Server-Side Request Forgery via scrape endpoint
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| refly-ai | refly | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Refly-ai | Refly |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.342% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Refly-ai
Refly-ai refly |
|
| Vendors & Products |
Refly-ai
Refly-ai refly |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Refly through 1.1.0 contains a server-side request forgery vulnerability in the POST /v1/misc/scrape endpoint that fetches caller-supplied URLs without validating the scheme, host, or resolved address. Authenticated attackers can make the backend issue requests to loopback, private, and link-local addresses including cloud metadata services to read page titles and descriptions of internal resources. | |
| Title | Refly through 1.1.0 Server-Side Request Forgery via scrape endpoint | |
| Weaknesses | CWE-918 | |
| References |
|
|
| Metrics |
cvssV3_1
|