Update dependency pycryptodomex to v3.19.1 [SECURITY] #35
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:
==3.18.0
->==3.19.1
GitHub Vulnerability Alerts
CVE-2023-52323
PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.
Release Notes
Legrandin/pycryptodome (pycryptodomex)
v3.19.1
: - ZeilCompare Source
Resolved issues
exploited to carry out a Manger attack. Thanks to Hubert Kario.
v3.19.0
: - UlmCompare Source
New features
update()
methods of TupleHash128 and TupleHash256 objectscan now hash multiple items (byte strings) at once.
Thanks to Sylvain Pelissier.
Crypto.Protocol.DH
.Resolved issues
cffi
, do not use it on Windows with Python 3.12+.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.