chore(deps): update dependency urllib3 to v2.2.2 [security] #119
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Trivy image scan report
|
| Package | ID | Severity | Installed Version | Fixed Version |
|---|---|---|---|---|
ca.uhn.hapi.fhir:org.hl7.fhir.r4 |
CVE-2024-51132 | HIGH | 6.3.23 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.r4 |
CVE-2024-52007 | HIGH | 6.3.23 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.utilities |
CVE-2024-51132 | HIGH | 6.3.23 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.utilities |
CVE-2024-52007 | HIGH | 6.3.23 | 6.4.0 |
No Misconfigurations found
🦙 MegaLinter status: ❌ ERROR
See detailed report in MegaLinter reports You could have same capabilities but better runtime performances if you request a new MegaLinter flavor. MegaLinter is graciously provided by |
miracum-bot
pushed a commit
that referenced
this pull request
Nov 19, 2024
## [2.1.7](v2.1.6...v2.1.7) (2024-11-19) ### Miscellaneous Chores * **deps:** refresh pip-compile outputs ([#122](#122)) ([77d4acf](77d4acf)) * **deps:** update all non-major dependencies ([#115](#115)) ([322d634](322d634)) * **deps:** update dependency certifi to v2024 [security] ([#120](#120)) ([bdf793c](bdf793c)) * **deps:** update dependency idna to v3.7 [security] ([#117](#117)) ([1b29b3e](1b29b3e)) * **deps:** update dependency requests to v2.32.2 [security] ([#118](#118)) ([a672aa7](a672aa7)) * **deps:** update dependency urllib3 to v2.2.2 [security] ([#119](#119)) ([a507559](a507559))
|
🎉 This PR is included in version 2.1.7 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.0.7->==2.2.2GitHub Vulnerability Alerts
CVE-2024-37891
When using urllib3's proxy support with
ProxyManager, theProxy-Authorizationheader is only sent to the configured proxy, as expected.However, when sending HTTP requests without using urllib3's proxy support, it's possible to accidentally configure the
Proxy-Authorizationheader even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat theProxy-AuthorizationHTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects.Because this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the
Proxy-Authorizationheader during cross-origin redirects to avoid the small chance that users are doing this on accident.Users should use urllib3's proxy support or disable automatic redirects to achieve safe processing of the
Proxy-Authorizationheader, but we still decided to strip the header by default in order to further protect users who aren't using the correct approach.Affected usages
We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited:
Proxy-Authorizationheader without using urllib3's built-in proxy support.Remediation
Proxy-Authorizationheader with urllib3'sProxyManager.redirects=Falsewhen sending requests.Proxy-Authorizationheader.Release Notes
urllib3/urllib3 (urllib3)
v2.2.2Compare Source
==================
Proxy-Authorizationheader to the list of headers to strip from requests when redirecting to a different host. As before, different headers can be set viaRetry.remove_headers_on_redirect.amtto read methods ofhttp.client.HTTPResponseas an alternative toNone. (#​3122 <https://github.com/urllib3/urllib3/issues/3122>__)typing.Self. (#​3363 <https://github.com/urllib3/urllib3/issues/3363>__)v2.2.1Compare Source
==================
InsecureRequestWarningwas emitted for HTTPS connections when using Emscripten. (#​3331 <https://github.com/urllib3/urllib3/issues/3331>__)HTTPConnectionPool.urlopento stop automatically casting non-proxy headers toHTTPHeaderDict. This change was premature as it did not apply to proxy headers andHTTPHeaderDictdoes not handle byte header values correctly yet. (#​3343 <https://github.com/urllib3/urllib3/issues/3343>__)InvalidChunkLengthtoProtocolErrorwhen response terminates before the chunk length is sent. (#​2860 <https://github.com/urllib3/urllib3/issues/2860>__)ProtocolErrorto be more verbose on incomplete reads with excess content. (#​3261 <https://github.com/urllib3/urllib3/issues/3261>__)v2.2.0Compare Source
==================
Emscripten and Pyodide <https://urllib3.readthedocs.io/en/latest/reference/contrib/emscripten.html>, including streaming support in cross-origin isolated browser environments where threading is enabled. (#​2951 <https://github.com/urllib3/urllib3/issues/2951>)HTTPResponse.read1()method. (#​3186 <https://github.com/urllib3/urllib3/issues/3186>__)#​3284 <https://github.com/urllib3/urllib3/issues/3284>__)when using proxy. (
#​2244 <https://github.com/urllib3/urllib3/issues/2244>__)HTTPConnection.proxy_is_verifiedandHTTPSConnection.proxy_is_verifiedto be always set to a boolean after connecting to a proxy. It could be
Nonein some cases previously. (#​3130 <https://github.com/urllib3/urllib3/issues/3130>__)headerspassed in a request withjson=would be mutated (#​3203 <https://github.com/urllib3/urllib3/issues/3203>__)HTTPSConnection.is_verifiedto be set toFalsewhen connectingfrom a HTTPS proxy to an HTTP target. It was set to
Truepreviously. (#​3267 <https://github.com/urllib3/urllib3/issues/3267>__)#​3268 <https://github.com/urllib3/urllib3/issues/3268>__)#​3325 <https://github.com/urllib3/urllib3/issues/3325>__)time with the
--integrationpytest flag. (#​3181 <https://github.com/urllib3/urllib3/issues/3181>__)v2.1.0Compare Source
==================
#​2680 <https://github.com/urllib3/urllib3/issues/2680>__)#​2681 <https://github.com/urllib3/urllib3/issues/2681>__)#​3143 <https://github.com/urllib3/urllib3/issues/3143>__)#​3065 <https://github.com/urllib3/urllib3/issues/3065>__)x-gzipcontent-encoding. (#​3174 <https://github.com/urllib3/urllib3/issues/3174>__)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 was generated by Mend Renovate. View the repository job log.