When doing TLS related transfers with reused easy or multi handles and altering the CURLSSLOPT_NO_PARTIALCHAIN 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.
{
"priority_reason": "This is rated as being low severity by Curl developers",
"binaries": [
{
"binary_name": "curl",
"binary_version": "8.5.0-2ubuntu10.7"
},
{
"binary_name": "libcurl3t64-gnutls",
"binary_version": "8.5.0-2ubuntu10.7"
},
{
"binary_name": "libcurl4-gnutls-dev",
"binary_version": "8.5.0-2ubuntu10.7"
},
{
"binary_name": "libcurl4-openssl-dev",
"binary_version": "8.5.0-2ubuntu10.7"
},
{
"binary_name": "libcurl4t64",
"binary_version": "8.5.0-2ubuntu10.7"
}
]
}
{
"priority_reason": "This is rated as being low severity by Curl developers",
"binaries": [
{
"binary_name": "curl",
"binary_version": "8.14.1-2ubuntu1.1"
},
{
"binary_name": "libcurl3t64-gnutls",
"binary_version": "8.14.1-2ubuntu1.1"
},
{
"binary_name": "libcurl4-gnutls-dev",
"binary_version": "8.14.1-2ubuntu1.1"
},
{
"binary_name": "libcurl4-openssl-dev",
"binary_version": "8.14.1-2ubuntu1.1"
},
{
"binary_name": "libcurl4t64",
"binary_version": "8.14.1-2ubuntu1.1"
}
]
}