CSRF protection could be tricked by forged X-Forwarded-Host header in KNIME Business Hub
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| KNIME | KNIME Business Hub | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.191% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.knime.com/security/advisories |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw in the cross-site request forgery (CSRF) prevention of KNIME Business Hub prior to version 1.19.0 allows an authenticated attacker to perform a CSRF attack with passive user interaction. This means the state of a resource could be changed without the user noticing. As a workaround, an API gateway for firewall in front of KNIME Business Hub could remove the X-Forwaded-For header from all incoming requests. | |
| Title | CSRF protection could be tricked by forged X-Forwarded-Host header in KNIME Business Hub | |
| Weaknesses | CWE-352 | |
| References |
| |
| Metrics |
cvssV4_0
|
No data.