Update dependency requests to v2.32.2 [SECURITY] - autoclosed

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
requests (source, changelog)	`==2.31.0` -> `==2.32.2`

GitHub Vulnerability Alerts

CVE-2024-35195

When making requests through a Requests Session, if the first request is made with verify=False to disable cert verification, all subsequent requests to the same origin will continue to ignore cert verification regardless of changes to the value of verify. This behavior will continue for the lifecycle of the connection in the connection pool.

Remediation

Any of these options can be used to remediate the current issue, we highly recommend upgrading as the preferred mitigation.

Upgrade to requests>=2.32.0.
For requests<2.32.0, avoid setting verify=False for the first request to a host while using a Requests Session.
For requests<2.32.0, call close() on Session objects to clear existing connections if verify=False is used.

Release Notes

psf/requests (requests)

### [`v2.32.2`](https://togithub.com/psf/requests/blob/HEAD/HISTORY.md#2322-2024-05-21) [Compare Source](https://togithub.com/psf/requests/compare/v2.32.1...v2.32.2) **Deprecations** - To provide a more stable migration for custom HTTPAdapters impacted by the CVE changes in 2.32.0, we've renamed `_get_connection` to a new public API, `get_connection_with_tls_context`. Existing custom HTTPAdapters will need to migrate their code to use this new API. `get_connection` is considered deprecated in all versions of Requests>=2.32.0. A minimal (2-line) example has been provided in the linked PR to ease migration, but we strongly urge users to evaluate if their custom adapter is subject to the same issue described in CVE-2024-35195. ([#6710](https://togithub.com/psf/requests/issues/6710)) ### [`v2.32.1`](https://togithub.com/psf/requests/blob/HEAD/HISTORY.md#2321-2024-05-20) [Compare Source](https://togithub.com/psf/requests/compare/v2.32.0...v2.32.1) **Bugfixes** - Add missing test certs to the sdist distributed on PyPI. ### [`v2.32.0`](https://togithub.com/psf/requests/blob/HEAD/HISTORY.md#2320-2024-05-20) [Compare Source](https://togithub.com/psf/requests/compare/v2.31.0...v2.32.0) **Security** - Fixed an issue where setting `verify=False` on the first request from a Session will cause subsequent requests to the *same origin* to also ignore cert verification, regardless of the value of `verify`. (https://github.com/psf/requests/security/advisories/GHSA-9wx4-h78v-vm56) **Improvements** - `verify=True` now reuses a global SSLContext which should improve request time variance between first and subsequent requests. It should also minimize certificate load time on Windows systems when using a Python version built with OpenSSL 3.x. ([#6667](https://togithub.com/psf/requests/issues/6667)) - Requests now supports optional use of character detection (`chardet` or `charset_normalizer`) when repackaged or vendored. This enables `pip` and other projects to minimize their vendoring surface area. The `Response.text()` and `apparent_encoding` APIs will default to `utf-8` if neither library is present. ([#6702](https://togithub.com/psf/requests/issues/6702)) **Bugfixes** - Fixed bug in length detection where emoji length was incorrectly calculated in the request content-length. ([#6589](https://togithub.com/psf/requests/issues/6589)) - Fixed deserialization bug in JSONDecodeError. ([#6629](https://togithub.com/psf/requests/issues/6629)) - Fixed bug where an extra leading `/` (path separator) could lead urllib3 to unnecessarily reparse the request URI. ([#6644](https://togithub.com/psf/requests/issues/6644)) **Deprecations** - Requests has officially added support for CPython 3.12 ([#6503](https://togithub.com/psf/requests/issues/6503)) - Requests has officially added support for PyPy 3.9 and 3.10 ([#6641](https://togithub.com/psf/requests/issues/6641)) - Requests has officially dropped support for CPython 3.7 ([#6642](https://togithub.com/psf/requests/issues/6642)) - Requests has officially dropped support for PyPy 3.7 and 3.8 ([#6641](https://togithub.com/psf/requests/issues/6641)) **Documentation** - Various typo fixes and doc improvements. **Packaging** - Requests has started adopting some modern packaging practices. The source files for the projects (formerly `requests`) is now located in `src/requests` in the Requests sdist. ([#6506](https://togithub.com/psf/requests/issues/6506)) - Starting in Requests 2.33.0, Requests will migrate to a PEP 517 build system using `hatchling`. This should not impact the average user, but extremely old versions of packaging utilities may have issues with the new packaging format.

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Hi there :wave:, @dryrunsecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Configured Codepaths Analyzer	:white_check_mark:	0 findings
Sensitive Files Analyzer	:grey_exclamation:	1 finding
IDOR Analyzer	:white_check_mark:	0 findings
SQL Injection Analyzer	:white_check_mark:	0 findings
Server-Side Request Forgery Analyzer	:white_check_mark:	0 findings
Secrets Analyzer	:white_check_mark:	0 findings
Authn/Authz Analyzer	:white_check_mark:	0 findings

[!Note] :green_circle: Risk threshold not exceeded.

Change Summary (click to expand)
The following is a summary of changes in this pull request made by me, your security buddy :robot:. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective. **Summary:** The provided code changes focus on updating the dependencies used in the Python application, specifically the `requests` library. The changes are made across three files: `setup.py`, `requirements.txt`, and `pyproject.toml`. The key changes include: 1. **`setup.py`**: The `requests` library version has been updated from `2.31.0` to `2.32.2`, which is a minor version update that typically includes bug fixes and improvements. 2. **`requirements.txt`**: Similar to the `setup.py` change, the `requests` library version has been updated from `2.31.0` to `2.32.2`. 3. **`pyproject.toml`**: The `requests` library version has been updated from `2.31.0` to `2.32.2`. From an application security perspective, these changes are generally positive as they help address any known vulnerabilities or security issues in the previous version of the `requests` library. Keeping dependencies up-to-date is a crucial aspect of maintaining the security of an application, as outdated dependencies can introduce security vulnerabilities that can be exploited by attackers. The `requests` library is a popular Python library for making HTTP requests, and it is commonly used in web applications and other network-based applications. Ensuring that the `requests` library is kept up-to-date is important to mitigate the risk of potential security vulnerabilities, such as injection vulnerabilities, SSL/TLS vulnerabilities, and denial-of-service (DoS) vulnerabilities. **Files Changed:** 1. **`setup.py`**: The `requests` library version has been updated from `2.31.0` to `2.32.2`. 2. **`requirements.txt`**: The `requests` library version has been updated from `2.31.0` to `2.32.2`. 3. **`pyproject.toml`**: The `requests` library version has been updated from `2.31.0` to `2.32.2`.

DryRun Security Summary

The provided code changes focus on updating the dependencies of the scsctl Python application, including updating the requests library to address potential security vulnerabilities and adding new dependencies such as uvicorn and fastapi to suggest the use of a modern, asynchronous architecture.

Expand for full summary

**Summary:** The provided code changes focus on updating the dependencies of the `scsctl` Python application. The key changes include: 1. Updating the `requests` library from version `2.31.0` to `2.32.2` across multiple files (setup.py, pyproject.toml, and requirements.txt). This is a positive change as it addresses potential security vulnerabilities in the previous version of the `requests` library. 2. Adding new dependencies, such as `uvicorn==0.23.2` and `fastapi==0.103.1`, which suggests that the application is using a modern, asynchronous architecture. While these additions are likely to improve the functionality and performance of the application, it is important to ensure that these new dependencies are also thoroughly reviewed and tested for any potential security vulnerabilities. Overall, the changes appear to be routine dependency updates and additions, which is a common practice in software development. However, it is crucial to maintain vigilance in reviewing all dependency updates and additions to ensure the ongoing security and integrity of the application. **Files Changed:** 1. `setup.py`: The version of the `requests` library has been updated from `2.31.0` to `2.32.2`. 2. `pyproject.toml`: The version of the `requests` library has been updated from `2.31.0` to `2.32.2`. 3. `requirements.txt`: The version of the `requests` library has been updated from `2.31.0` to `2.32.2`. Additionally, new dependencies have been added, including `uvicorn==0.23.2` and `fastapi==0.103.1`.

Code Analysis

We ran 9 analyzers against 3 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

:green_circle: Risk threshold not exceeded.

View PR in the DryRun Dashboard.

intelops / scsctl