When doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously was used to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent POST request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Curl | Haxx | * | 7.86.0 (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 | * |
| Red Hat Enterprise Linux 9 | RedHat | curl-0:7.76.1-19.el9_1.1 | * |
| Red Hat Enterprise Linux 9 | RedHat | curl-0:7.76.1-19.el9_1.1 | * |
| Red Hat Enterprise Linux 9.0 Extended Update Support | RedHat | curl-0:7.76.1-14.el9_0.6 | * |
| Text-Only JBCS | RedHat | curl | * |
| Curl | Ubuntu | bionic | * |
| Curl | Ubuntu | devel | * |
| Curl | Ubuntu | esm-infra/xenial | * |
| Curl | Ubuntu | focal | * |
| Curl | Ubuntu | jammy | * |
| Curl | Ubuntu | kinetic | * |
| Curl | Ubuntu | trusty | * |
| Curl | Ubuntu | trusty/esm | * |
| Curl | Ubuntu | xenial | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.