Update dependency idna to v3 [SECURITY] - autoclosed #465
Conversation
This file contains hidden or 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
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypi-idna-vulnerability
branch
from
b232110 to
b40a40f
Compare
renovate
bot
force-pushed
the
renovate/pypi-idna-vulnerability
branch
4 times, most recently
from
4558e8e to
8d7ac5d
Compare
renovate
bot
force-pushed
the
renovate/pypi-idna-vulnerability
branch
2 times, most recently
from
954028b to
2c74142
Compare
renovate
bot
force-pushed
the
renovate/pypi-idna-vulnerability
branch
from
2c74142 to
d3e9ce6
Compare
renovate
bot
changed the title
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.10→==3.7GitHub Vulnerability Alerts
CVE-2024-3651
Impact
A specially crafted argument to the
idna.encode()function could consume significant resources. This may lead to a denial-of-service.Patches
The function has been refined to reject such strings without the associated resource consumption in version 3.7.
Workarounds
Domain names cannot exceed 253 characters in length, if this length limit is enforced prior to passing the domain to the
idna.encode()function it should no longer consume significant resources. This is triggered by arbitrarily large inputs that would not occur in normal usage, but may be passed to the library assuming there is no preliminary input validation by the higher-level application.References
Release Notes
kjd/idna (idna)
v3.7Compare Source
What's Changed
Thanks to Guido Vranken for reporting the issue.
Full Changelog: kjd/idna@v3.6...v3.7
v3.6Compare Source
v3.5Compare Source
v3.4Compare Source
v3.3Compare Source
v3.2Compare Source
v3.1Compare Source
v3.0Compare Source
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 is behind base branch, 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.