Host filesystem path disclosure via DNS rebinding
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| tidewave-ai | tidewave | unaffected |
|
||||||
| tidewave-ai | tidewave | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tidewave-ai | Tidewave |
|
||||||||
| Tidewave-ai | Tidewave |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.368% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An attacker can read the name of filesystem paths of your application present via Tidewave configuration via /tidewave/connect or via the rendered toolbar. Neither response checks the Host header. A web page that rebinds its own domain to the loopback address can therefore read the tag with a same-origin request, which carries no Origin header. The paths usually reveal the local username and the project layout. This issue affects tidewave: from 0.8.0 before 0.9.2. | |
| Title | Host filesystem path disclosure via DNS rebinding | |
| First Time appeared |
Tidewave-ai
Tidewave-ai tidewave |
|
| Weaknesses | CWE-497 | |
| CPEs | cpe:2.3:a:tidewave-ai:tidewave:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Tidewave-ai
Tidewave-ai tidewave |
|
| References |
| |
| Metrics |
cvssV4_0
|