Skip to content
This repository has been archived by the owner on Apr 1, 2024. It is now read-only.

Update dependency pycryptodome to v3.19.1 [SECURITY] #85

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pycryptodome (source, changelog) ==3.19.0 -> ==3.19.1 age adoption passing confidence

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 (pycryptodome)

v3.19.1: - Zeil

Compare Source

Resolved issues

  • Fixed a side-channel leakage with OAEP decryption that could be
    exploited to carry out a Manger attack. Thanks to Hubert Kario.

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.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/pypi-pycryptodome-vulnerability branch 3 times, most recently from c4830ad to bcd96e6 Compare January 21, 2024 22:15
@renovate renovate bot force-pushed the renovate/pypi-pycryptodome-vulnerability branch from bcd96e6 to 1e856e2 Compare January 21, 2024 22:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants