curl inadvertently kept the SSL session ID for connections in its cache even when the verify status (OCSP stapling) test failed. A subsequent transfer to the same hostname could then succeed if the session ID cache was still fresh, which then skipped the verify status check.
{ "availability": "No subscription required", "ubuntu_priority": "low", "binaries": [ { "binary_version": "8.5.0-2ubuntu2", "binary_name": "curl" }, { "binary_version": "8.5.0-2ubuntu2", "binary_name": "curl-dbgsym" }, { "binary_version": "8.5.0-2ubuntu2", "binary_name": "libcurl3-gnutls" }, { "binary_version": "8.5.0-2ubuntu2", "binary_name": "libcurl3-gnutls-dbgsym" }, { "binary_version": "8.5.0-2ubuntu2", "binary_name": "libcurl4" }, { "binary_version": "8.5.0-2ubuntu2", "binary_name": "libcurl4-dbgsym" }, { "binary_version": "8.5.0-2ubuntu2", "binary_name": "libcurl4-doc" }, { "binary_version": "8.5.0-2ubuntu2", "binary_name": "libcurl4-gnutls-dev" }, { "binary_version": "8.5.0-2ubuntu2", "binary_name": "libcurl4-openssl-dev" } ], "priority_reason": "Upstream Curl developers have rated this as being low severity" }