wrong reuse of SMB connection
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.18.08.17.08.16.08.15.08.14.1| No fix yet |
libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a network transfer operation that was requested by an application could wrongfully reuse an existing SMB connection to the same server that was using a different "share" than the new subsequent transfer should.
This could in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place. When this happens, the same credentials are used and the server name is the same.
From the CVE record · curl
libcurl can mistakenly reuse an SMB connection for a subsequent transfer to a different share on the same server. When an application makes such a request, it may download the wrong file or upload a file to the wrong place; the reused connection uses the same credentials.
Engineers running applications that use libcurl for SMB(S) transfers should check their installations; affected versions were not provided.