deps: update dependency requests to v2.32.0 [security] #2791
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trusted-contributions-gcf
bot
added
kokoro:force-run
gcf-owl-bot
bot
removed
the
owlbot:run
|
|
|
/gcbrun |
JoeWang1127
approved these changes
May 21, 2024
lqiu96
pushed a commit
that referenced
this pull request
May 22, 2024
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [requests](https://requests.readthedocs.io) ([source](https://github.com/psf/requests), [changelog](https://github.com/psf/requests/blob/master/HISTORY.md)) | `==2.31.0` -> `==2.32.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. ### GitHub Vulnerability Alerts #### [CVE-2024-35195](https://github.com/psf/requests/security/advisories/GHSA-9wx4-h78v-vm56) 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. ### Related Links * [https://github.com/psf/requests/pull/6655](https://github.com/psf/requests/pull/6655) --- ### Release Notes <details> <summary>psf/requests (requests)</summary> ### [`v2.32.0`](https://github.com/psf/requests/blob/HEAD/HISTORY.md#2320-2024-05-20) [Compare Source](https://github.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`. (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://github.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://github.com/psf/requests/issues/6702)) **Bugfixes** - Fixed bug in length detection where emoji length was incorrectly calculated in the request content-length. ([#​6589](https://github.com/psf/requests/issues/6589)) - Fixed deserialization bug in JSONDecodeError. ([#​6629](https://github.com/psf/requests/issues/6629)) - Fixed bug where an extra leading `/` (path separator) could lead urllib3 to unnecessarily reparse the request URI. ([#​6644](https://github.com/psf/requests/issues/6644)) **Deprecations** - Requests has officially added support for CPython 3.12 ([#​6503](https://github.com/psf/requests/issues/6503)) - Requests has officially added support for PyPy 3.9 and 3.10 ([#​6641](https://github.com/psf/requests/issues/6641)) - Requests has officially dropped support for CPython 3.7 ([#​6642](https://github.com/psf/requests/issues/6642)) - Requests has officially dropped support for PyPy 3.7 and 3.8 ([#​6641](https://github.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://github.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. </details> --- ### 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 this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/googleapis/sdk-platform-java). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zNjguMTAiLCJ1cGRhdGVkSW5WZXIiOiIzNy4zNjguMTAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
](https://renovatebot.com){kind=link}
diegomarquezp
pushed a commit
that referenced
this pull request
May 31, 2024
🤖 I have created a release *beep* *boop* --- <details><summary>2.41.0</summary> ## [2.41.0](v2.40.1...v2.41.0) (2024-05-31) ### Features * add a github client ([#2747](#2747)) ([f8ea0a0](f8ea0a0)) * generate proto-only repository ([#2720](#2720)) ([f7a5161](f7a5161)) ### Bug Fixes * [#2785](#2785). ([599f5da](599f5da)) ### Dependencies * update dependency com.google.api-client:google-api-client-bom to v2.6.0 ([#2782](#2782)) ([5bc8928](5bc8928)) * update dependency com.google.cloud.opentelemetry:detector-resources-support to v0.29.0 ([#2831](#2831)) ([6c1dbfc](6c1dbfc)) * update dependency com.google.code.gson:gson to v2.11.0 ([#2786](#2786)) ([91f3254](91f3254)) * update dependency com.google.code.gson:gson to v2.11.0 ([#2787](#2787)) ([e81893c](e81893c)) * update dependency com.google.errorprone:error_prone_annotations to v2.28.0 ([#2835](#2835)) ([b8f11b1](b8f11b1)) * update dependency com.google.errorprone:error_prone_annotations to v2.28.0 ([#2838](#2838)) ([5c46f3f](5c46f3f)) * update dependency net.bytebuddy:byte-buddy to v1.14.16 ([#2797](#2797)) ([dfedafc](dfedafc)) * update dependency net.bytebuddy:byte-buddy to v1.14.17 ([#2828](#2828)) ([6eb9041](6eb9041)) * update dependency org.checkerframework:checker-qual to v3.43.0 ([#2730](#2730)) ([b7fa736](b7fa736)) * update dependency requests to v2.32.0 [security] ([#2791](#2791)) ([c2ea6cc](c2ea6cc)) * update dependency watchdog to v4.0.1 ([#2800](#2800)) ([d5771dd](d5771dd)) * update google api dependencies ([#2672](#2672)) ([6643536](6643536)) * update google http client dependencies to v1.44.2 ([#2783](#2783)) ([dee7e00](dee7e00)) * update googleapis/java-cloud-bom digest to 59c776b ([#2827](#2827)) ([03b3eb4](03b3eb4)) * update netty dependencies to v4.1.110.final ([#2796](#2796)) ([d1aaa68](d1aaa68)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
lqiu96
pushed a commit
that referenced
this pull request
Jun 10, 2024
🤖 I have created a release *beep* *boop* --- <details><summary>2.41.0</summary> ## [2.41.0](v2.40.1...v2.41.0) (2024-05-31) ### Features * add a github client ([#2747](#2747)) ([f8ea0a0](f8ea0a0)) * generate proto-only repository ([#2720](#2720)) ([f7a5161](f7a5161)) ### Bug Fixes * [#2785](#2785). ([599f5da](599f5da)) ### Dependencies * update dependency com.google.api-client:google-api-client-bom to v2.6.0 ([#2782](#2782)) ([5bc8928](5bc8928)) * update dependency com.google.cloud.opentelemetry:detector-resources-support to v0.29.0 ([#2831](#2831)) ([6c1dbfc](6c1dbfc)) * update dependency com.google.code.gson:gson to v2.11.0 ([#2786](#2786)) ([91f3254](91f3254)) * update dependency com.google.code.gson:gson to v2.11.0 ([#2787](#2787)) ([e81893c](e81893c)) * update dependency com.google.errorprone:error_prone_annotations to v2.28.0 ([#2835](#2835)) ([b8f11b1](b8f11b1)) * update dependency com.google.errorprone:error_prone_annotations to v2.28.0 ([#2838](#2838)) ([5c46f3f](5c46f3f)) * update dependency net.bytebuddy:byte-buddy to v1.14.16 ([#2797](#2797)) ([dfedafc](dfedafc)) * update dependency net.bytebuddy:byte-buddy to v1.14.17 ([#2828](#2828)) ([6eb9041](6eb9041)) * update dependency org.checkerframework:checker-qual to v3.43.0 ([#2730](#2730)) ([b7fa736](b7fa736)) * update dependency requests to v2.32.0 [security] ([#2791](#2791)) ([c2ea6cc](c2ea6cc)) * update dependency watchdog to v4.0.1 ([#2800](#2800)) ([d5771dd](d5771dd)) * update google api dependencies ([#2672](#2672)) ([6643536](6643536)) * update google http client dependencies to v1.44.2 ([#2783](#2783)) ([dee7e00](dee7e00)) * update googleapis/java-cloud-bom digest to 59c776b ([#2827](#2827)) ([03b3eb4](03b3eb4)) * update netty dependencies to v4.1.110.final ([#2796](#2796)) ([d1aaa68](d1aaa68)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==2.31.0->==2.32.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2024-35195
When making requests through a Requests
Session, if the first request is made withverify=Falseto disable cert verification, all subsequent requests to the same origin will continue to ignore cert verification regardless of changes to the value ofverify. 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.
requests>=2.32.0.requests<2.32.0, avoid settingverify=Falsefor the first request to a host while using a Requests Session.requests<2.32.0, callclose()onSessionobjects to clear existing connections ifverify=Falseis used.Related Links
Release Notes
psf/requests (requests)
v2.32.0Compare Source
Security
verify=Falseon the first request from aSession will cause subsequent requests to the same origin to also ignore
cert verification, regardless of the value of
verify.(GHSA-9wx4-h78v-vm56)
Improvements
verify=Truenow reuses a global SSLContext which should improverequest 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)
(
chardetorcharset_normalizer) when repackaged or vendored.This enables
pipand other projects to minimize their vendoringsurface area. The
Response.text()andapparent_encodingAPIswill default to
utf-8if neither library is present. (#6702)Bugfixes
calculated in the request content-length. (#6589)
/(path separator) could leadurllib3 to unnecessarily reparse the request URI. (#6644)
Deprecations
Documentation
Packaging
The source files for the projects (formerly
requests) is now locatedin
src/requestsin the Requests sdist. (#6506)using
hatchling. This should not impact the average user, but extremely oldversions 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.