predictable WebSocket mask
curl
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
8.13.08.12.18.12.0| No fix yet |
curl's WebSocket code did not update the 32-bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection.
A predictable mask pattern allows for a malicious server to induce traffic between the two communicating parties that could be interpreted by an involved proxy (configured or transparent) as genuine, real, HTTP traffic with content and thereby poison its cache. That cached poisoned content could then be served to all users of that proxy.
From the CVE record · curl
curl's WebSocket code reuses a fixed mask across outgoing frames instead of updating it for each frame. A malicious server could exploit the predictable mask to make traffic appear to a configured or transparent proxy as genuine HTTP content, poisoning its cache for other users.
Engineers running curl with WebSocket connections that pass through a proxy should check their installations; affected versions were not provided.