Taipy through 4.1.1 Cross-Site WebSocket Hijacking via Wildcard socket.io CORS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Avaiga | taipy | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Taipy | Taipy |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.234% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Taipy configures its socket.io server with wildcard CORS origin and credential flag enabled, allowing any web page to establish credentialed WebSocket connections to victim applications. Attackers can open socket.io sessions from arbitrary domains and invoke state variable modifications and action callbacks without CSRF protection. | |
| Title | Taipy through 4.1.1 Cross-Site WebSocket Hijacking via Wildcard socket.io CORS | |
| First Time appeared |
Taipy
Taipy taipy |
|
| Weaknesses | CWE-1385 | |
| CPEs | cpe:2.3:a:taipy:taipy:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Taipy
Taipy taipy |
|
| References |
| |
| Metrics |
cvssV3_1
|