broken TLS options for threaded LDAPS
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.16.08.15.08.14.18.14.08.13.0| No fix yet |
When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers.
Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.
From the CVE record · curl
In multi-threaded LDAPS transfers, changing libcurl TLS options in one thread can also affect transfers being set up in other threads. If certificate verification is disabled for one transfer, it could unintentionally be disabled for those other transfers as well.
Engineers running curl applications that use libcurl for multi-threaded LDAPS transfers should check their deployments; affected versions were not provided.