REDHAT-BUG-2426408: Low severity libcurl libcurl vulnerability
When doing TLS related transfers with re-used easy or multi handles and altering the CURLSSLOPTNOPARTIALCHAIN option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl find and accept a trust chain that it otherwise would not.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed to this behavior?
The described condition affects TLS transfers that reuse easy or multi handles and alter the CURLSSLOPT_NO_PARTIALCHAIN option. The data does not establish impact for transfers that do not reuse handles or do not change that option.
What can be done when an update cannot be applied immediately?
Avoid changing CURLSSLOPT_NO_PARTIALCHAIN on reused easy or multi handles. Use separate handles for transfers that require different partial-chain behavior so a cached CA store is not reused with the opposite setting.
Does the issue depend on enabling or disabling the option?
The data states that altering the option can cause reuse of a CA store whose partial-chain setting is reversed. It does not specify whether one direction of the option change is more affected than the other.