Scrapy is a high-level web crawling and scraping framework for Python. If you use HttpAuthMiddleware (i.e. the http_user and http_pass spider attributes) for HTTP authentication, all requests will expose your credentials to the request target. This includes requests generated by Scrapy components, such as robots.txt requests sent by Scrapy when the ROBOTSTXT_OBEY setting is set to True, or as requests reached through redirects. Upgrade to Scrapy 2.5.1 and use the new http_auth_domain spider attribute to control which domains are allowed to receive the configured HTTP authentication credentials. If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.5.1 is not an option, you may upgrade to Scrapy 1.8.1 instead. If you cannot upgrade, set your HTTP authentication credentials on a per-request basis, using for example the w3lib.http.basic_auth_header function to convert your credentials into a value that you can assign to the Authorization header of your request, instead of defining your credentials globally using HttpAuthMiddleware.
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 |
|---|---|---|---|
| Scrapy | Scrapy | * | 1.8.1 (excluding) |
| Scrapy | Scrapy | 2.0.0 (including) | 2.5.1 (excluding) |
| Python-scrapy | Ubuntu | bionic | * |
| Python-scrapy | Ubuntu | devel | * |
| Python-scrapy | Ubuntu | esm-apps/bionic | * |
| Python-scrapy | Ubuntu | esm-apps/focal | * |
| Python-scrapy | Ubuntu | esm-apps/jammy | * |
| Python-scrapy | Ubuntu | esm-apps/noble | * |
| Python-scrapy | Ubuntu | focal | * |
| Python-scrapy | Ubuntu | hirsute | * |
| Python-scrapy | Ubuntu | impish | * |
| Python-scrapy | Ubuntu | jammy | * |
| Python-scrapy | Ubuntu | kinetic | * |
| Python-scrapy | Ubuntu | lunar | * |
| Python-scrapy | Ubuntu | mantic | * |
| Python-scrapy | Ubuntu | noble | * |
| Python-scrapy | Ubuntu | oracular | * |
| Python-scrapy | Ubuntu | trusty | * |
| Python-scrapy | Ubuntu | upstream | * |
| Python-scrapy | 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.