securedrop-proxy origin limitation can be bypassed with redirects
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| freedomofpress | securedrop-client | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Freedomofpress | Securedrop-client |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.309% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Freedomofpress
Freedomofpress securedrop-client |
|
| Vendors & Products |
Freedomofpress
Freedomofpress securedrop-client |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | SecureDrop Client is a desktop app for journalists to securely communicate with sources and handle submissions on the SecureDrop Workstation. Prior to version 1.3.1, a malicious SecureDrop Server could bypass securedrop-proxy's origin limitation by responding with cross-origin redirects. SecureDrop Server itself has multiple layers of built-in hardening, and is a dedicated physical machine exposed on the internet only via Tor hidden services for the Source and Journalist interfaces, and optionally via remote SSH access over another Tor hidden service. A newsroom's SecureDrop Workstation communicates only with its own dedicated SecureDrop Server. Version 1.3.1 fixes the issue. | |
| Title | securedrop-proxy origin limitation can be bypassed with redirects | |
| Weaknesses | CWE-601 | |
| References |
| |
| Metrics |
cvssV3_1
|