urllib3 is a user-friendly HTTP client library for Python. urllib3 previously wouldnt remove the HTTP request body when an HTTP redirect response using status 301, 302, or 303 after the request had its method changed from one that could accept a request body (like POST) to GET as is required by HTTP RFCs. Although this behavior is not specified in the section for redirects, it can be inferred by piecing together information from different sections and we have observed the behavior in other major HTTP client implementations like curl and web browsers. Because the vulnerability requires a previously trusted service to become compromised in order to have an impact on confidentiality we believe the exploitability of this vulnerability is low. Additionally, many users arent putting sensitive data in HTTP request bodies, if this is the case then this vulnerability isnt exploitable. Both of the following conditions must be true to be affected by this vulnerability: 1. Using urllib3 and submitting sensitive information in the HTTP request body (such as form data or JSON) and 2. The origin service is compromised and starts redirecting using 301, 302, or 303 to a malicious peer or the redirected-to service becomes compromised. This issue has been addressed in versions 1.26.18 and 2.0.7 and users are advised to update to resolve this issue. Users unable to update should disable redirects for services that arent expecting to respond with redirects with redirects=False and disable automatic redirects with redirects=False and handle 301, 302, and 303 redirects manually by stripping the HTTP request body.
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 |
|---|---|---|---|
| Urllib3 | Python | * | 1.26.18 (excluding) |
| Urllib3 | Python | 2.0.0 (including) | 2.0.7 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | fence-agents-0:4.2.1-129.el8 | * |
| Red Hat Enterprise Linux 8 | RedHat | container-tools:rhel8-8100020240227110532.82888897 | * |
| Red Hat Enterprise Linux 8 | RedHat | resource-agents-0:4.9.0-54.el8 | * |
| Red Hat Enterprise Linux 8 | RedHat | python-urllib3-0:1.24.2-5.el8_9.2 | * |
| Red Hat Enterprise Linux 8.6 Extended Update Support | RedHat | python-urllib3-0:1.24.2-5.el8_6.1 | * |
| Red Hat Enterprise Linux 8.8 Extended Update Support | RedHat | python-urllib3-0:1.24.2-5.el8_8.1 | * |
| Red Hat Enterprise Linux 9 | RedHat | fence-agents-0:4.10.0-62.el9 | * |
| Red Hat Enterprise Linux 9 | RedHat | python-urllib3-0:1.26.5-3.el9_3.1 | * |
| Red Hat Enterprise Linux 9.0 Extended Update Support | RedHat | fence-agents-0:4.10.0-20.el9_0.11 | * |
| Red Hat OpenStack Platform 17.1 for RHEL 8 | RedHat | python-urllib3-0:1.25.10-6.el8ost | * |
| Red Hat Satellite 6.14 for RHEL 8 | RedHat | python-urllib3-0:1.26.18-0.1.el8pc | * |
| Red Hat Satellite 6.14 for RHEL 8 | RedHat | python-urllib3-0:1.26.18-0.1.el8pc | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/cephcsi-rhel9:v4.15.0-37 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/mcg-core-rhel9:v4.15.0-68 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/mcg-operator-bundle:v4.15.0-158 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/mcg-rhel9-operator:v4.15.0-39 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/ocs-client-console-rhel9:v4.15.0-58 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/ocs-client-operator-bundle:v4.15.0-158 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/ocs-client-rhel9-operator:v4.15.0-13 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/ocs-metrics-exporter-rhel9:v4.15.0-81 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/ocs-operator-bundle:v4.15.0-158 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/ocs-rhel9-operator:v4.15.0-79 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-cli-rhel9:v4.15.0-22 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-console-rhel9:v4.15.0-57 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-cosi-sidecar-rhel9:v4.15.0-6 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-csi-addons-operator-bundle:v4.15.0-158 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-csi-addons-rhel9-operator:v4.15.0-15 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-csi-addons-sidecar-rhel9:v4.15.0-15 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-multicluster-console-rhel9:v4.15.0-54 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-multicluster-operator-bundle:v4.15.0-158 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-multicluster-rhel9-operator:v4.15.0-10 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-must-gather-rhel9:v4.15.0-26 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-operator-bundle:v4.15.0-158 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-rhel9-operator:v4.15.0-19 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odr-cluster-operator-bundle:v4.15.0-158 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odr-hub-operator-bundle:v4.15.0-158 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odr-rhel9-operator:v4.15.0-21 | * |
| RHODF-4.15-RHEL-9 | RedHat | odf4/rook-ceph-rhel9-operator:v4.15.0-103 | * |
| Python-pip | Ubuntu | bionic | * |
| Python-pip | Ubuntu | esm-apps/bionic | * |
| Python-pip | Ubuntu | esm-apps/xenial | * |
| Python-pip | Ubuntu | focal | * |
| Python-pip | Ubuntu | jammy | * |
| Python-pip | Ubuntu | lunar | * |
| Python-pip | Ubuntu | mantic | * |
| Python-pip | Ubuntu | trusty | * |
| Python-pip | Ubuntu | xenial | * |
| Python-urllib3 | Ubuntu | bionic | * |
| Python-urllib3 | Ubuntu | esm-infra/bionic | * |
| Python-urllib3 | Ubuntu | esm-infra/xenial | * |
| Python-urllib3 | Ubuntu | focal | * |
| Python-urllib3 | Ubuntu | jammy | * |
| Python-urllib3 | Ubuntu | lunar | * |
| Python-urllib3 | Ubuntu | mantic | * |
| Python-urllib3 | Ubuntu | trusty | * |
| Python-urllib3 | Ubuntu | upstream | * |
| Python-urllib3 | 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.