Описание
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.
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2024-0853
- https://hackerone.com/reports/2298922
- https://curl.se/docs/CVE-2024-0853.html
- https://curl.se/docs/CVE-2024-0853.json
- https://security.netapp.com/advisory/ntap-20240307-0004
- https://security.netapp.com/advisory/ntap-20240426-0009
- https://security.netapp.com/advisory/ntap-20240503-0012
Связанные уязвимости
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.
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.
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.
curl inadvertently kept the SSL session ID for connections in its cach ...