libcurl provides the CURLOPT_CERTINFO option to allow applications torequest details to be returned about a servers certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Curl | Haxx | * | 7.83.1 (excluding) |
| JBoss Core Services for RHEL 8 | RedHat | jbcs-httpd24-curl-0:7.86.0-2.el8jbcs | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-curl-0:7.86.0-2.el7jbcs | * |
| Text-Only JBCS | RedHat | jbcs-httpd24-curl | * |
| Curl | Ubuntu | bionic | * |
| Curl | Ubuntu | devel | * |
| Curl | Ubuntu | esm-infra-legacy/trusty | * |
| Curl | Ubuntu | esm-infra/bionic | * |
| Curl | Ubuntu | esm-infra/focal | * |
| Curl | Ubuntu | esm-infra/xenial | * |
| Curl | Ubuntu | focal | * |
| Curl | Ubuntu | impish | * |
| Curl | Ubuntu | jammy | * |
| Curl | Ubuntu | trusty/esm | * |
| Curl | Ubuntu | upstream | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.