ClaraVerse through 0.3.1 SSRF Protection Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| claraverse-space | ClaraVerse | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Claraverse-space | Claraverse |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.233% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Claraverse-space
Claraverse-space claraverse |
|
| Vendors & Products |
Claraverse-space
Claraverse-space claraverse |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ClaraVerse through 0.3.1 contains server-side request forgery protection bypasses in the download_file and scrape_web agent tools. Authenticated users can bypass hostname validation and IPv6 transition address filtering to make the server request internal services and cloud instance metadata endpoints. | |
| Title | ClaraVerse through 0.3.1 SSRF Protection Bypass | |
| Weaknesses | CWE-918 | |
| References |
|
|
| Metrics |
cvssV3_1
|