sending old referer
curl
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared. While the documentation states that passing NULL to `CURLOPT_REFERER` suppresses the header, the option failed to clear the internal state. As a result, the previous referrer string was erroneously reused and sent in subsequent requests, potentially leaking sensitive information to unintended servers.
From the CVE record · curl
libcurl can retain an HTTP `Referer:` header after an application clears it by passing NULL to `CURLOPT_REFERER`. On subsequent requests, it may send the previous referrer to an unintended server, potentially exposing sensitive information.
Teams using curl or libcurl should check applications that set and then clear `CURLOPT_REFERER`; affected versions were not specified.