Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency cryptography to v44 [SECURITY] #34

Open
wants to merge 1 commit into
base: 6/edge
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 4, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cryptography (changelog) ^42.0.5 -> ^44.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

GHSA-h4gh-qq45-vh27

pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 37.0.0-43.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20240903.txt.

If you are building cryptography source ("sdist") then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.

CVE-2024-12797

pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 42.0.0-44.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20250211.txt.

If you are building cryptography source ("sdist") then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.


Release Notes

pyca/cryptography (cryptography)

v44.0.1

Compare Source

v44.0.0

Compare Source

v43.0.3

Compare Source

v43.0.1

Compare Source

v43.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "" in timezone Etc/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.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team September 4, 2024 00:33
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 1bcc6ac to 82b3502 Compare October 17, 2024 08:12
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 3 times, most recently from 5a7ef2f to 87e2cef Compare November 12, 2024 23:13
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 87e2cef to ddbf5d5 Compare December 12, 2024 04:18
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 5 times, most recently from 967eb11 to ceb5536 Compare January 15, 2025 15:14
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 3 times, most recently from e52fead to 6916d2a Compare January 22, 2025 11:09
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 6916d2a to 31bd9ee Compare January 28, 2025 15:09
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 31bd9ee to 364721a Compare February 11, 2025 15:47
@renovate renovate bot changed the title Update dependency cryptography to v43 [SECURITY] Update dependency cryptography to v44 [SECURITY] Feb 12, 2025
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 364721a to be0a5b8 Compare February 12, 2025 02:11
Copy link
Author

renovate bot commented Feb 12, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
Updating dependencies
Resolving dependencies...

Creating virtualenv non-package-mode-6zD_bwme-py3.13 in /home/ubuntu/.cache/pypoetry/virtualenvs

Because no versions of mongo-charms-single-kernel match >0.0.1,<0.0.2 || >0.0.2,<0.1.0
 and mongo-charms-single-kernel (0.0.2) depends on cryptography (>=42.0.5,<42.1.0), mongo-charms-single-kernel (>0.0.1,<0.1.0) requires cryptography (>=42.0.5,<42.1.0).
And because mongo-charms-single-kernel (0.0.1) depends on cryptography (>=42.0.5,<42.1.0), mongo-charms-single-kernel (>=0.0.1,<0.1.0) requires cryptography (>=42.0.5,<42.1.0).
So, because non-package-mode depends on both mongo-charms-single-kernel (>=0.0.1,<0.1.0) and cryptography (^44.0.0), version solving failed.

@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from be0a5b8 to 419c5df Compare February 12, 2025 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants