password leak with netrc and user in URL
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.19.08.18.08.17.08.16.08.15.0| No fix yet |
When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file for that host if such a one exists and there is no match for the specified user.
From the CVE record · curl
curl can select the wrong password from a `.netrc` file when a URL specifies a username without a password. If that username has no matching entry but another user has an entry for the host, curl can use that other user's password. This requires curl to be configured to use `.netrc`; the input does not establish an authentication requirement or attacker-controlled route to exploitation.
Anyone running curl with `.netrc` credentials should check their usage; affected versions were not provided.