Skip to content
New issue

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

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

Already on GitHub? # to your account

chore(deps): update dependency cryptography to v44 [security] #946

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 11, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cryptography (changelog) ==43.0.1 -> ==44.0.1 age adoption passing confidence

Review

  • Updates have been tested and work
  • If updates are AWS related, versions match the infrastructure (e.g. Lambda runtime, database, etc.)

GitHub Vulnerability Alerts

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


Configuration

📅 Schedule: Branch creation - "" in timezone America/Montreal, 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 force-pushed the renovate/pypi-cryptography-vulnerability branch 9 times, most recently from 04c2175 to 381c5f0 Compare February 18, 2025 14:28
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 3 times, most recently from 76823da to 3f841a5 Compare February 26, 2025 13:28
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 4 times, most recently from dadaa6b to ff26b7b Compare March 6, 2025 15:52
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from ff26b7b to 7ef24ff Compare March 6, 2025 17:12
Copy link

github-actions bot commented Mar 6, 2025

Staging: pr_review

✅   Terraform Init: success
✅   Terraform Validate: success
✅   Terraform Format: success
❌   Terraform Plan: failed
❌   Conftest: failed

Show plan
Error: Error acquiring the state lock

Error message: operation error DynamoDB: PutItem, https response error
StatusCode: 400, RequestID:
4AGTHA6I5KKBDIBVSJJSTI1VIBVV4KQNSO5AEMVJF66Q9ASUAAJG,
ConditionalCheckFailedException: The conditional request failed
Lock Info:
  ID:        a458f7e4-1b71-e1b8-2059-97d8adfb2ed0
  Path:      forms-staging-tfstate/cloud/pr_review/terraform.tfstate
  Operation: OperationTypePlan
  Who:       runner@fv-az1928-382
  Version:   1.10.5
  Created:   2025-03-06 17:13:42.320076215 +0000 UTC
  Info:      


Terraform acquires a state lock to protect the state from being written
by multiple users at the same time. Please resolve the issue above and try
again. For most commands, you can disable locking with the "-lock=false"
flag, but this is not recommended.
�[0;90m17:13:44.238�[0m �[0;31mERROR �[0m terraform invocation failed in ./.terragrunt-cache/7p-EsC9XJydLSepQWsS3iOze-tc/-syjFrdAaB-6kNXhMmF1nXBOp7o/pr_review
�[0;90m17:13:44.239�[0m �[0;31mERROR �[0m error occurred:

* Failed to execute "terraform plan -no-color -input=false -out=plan.tfplan" in ./.terragrunt-cache/7p-EsC9XJydLSepQWsS3iOze-tc/-syjFrdAaB-6kNXhMmF1nXBOp7o/pr_review
  
  Error: Error acquiring the state lock
  
  Error message: operation error DynamoDB: PutItem, https response error
  StatusCode: 400, RequestID:
  4AGTHA6I5KKBDIBVSJJSTI1VIBVV4KQNSO5AEMVJF66Q9ASUAAJG,
  ConditionalCheckFailedException: The conditional request failed
  Lock Info:
    ID:        a458f7e4-1b71-e1b8-2059-97d8adfb2ed0
    Path:      forms-staging-tfstate/cloud/pr_review/terraform.tfstate
    Operation: OperationTypePlan
    Who:       runner@fv-az1928-382
    Version:   1.10.5
    Created:   2025-03-06 17:13:42.320076215 +0000 UTC
    Info:      
  
  
  Terraform acquires a state lock to protect the state from being written
  by multiple users at the same time. Please resolve the issue above and try
  again. For most commands, you can disable locking with the "-lock=false"
  flag, but this is not recommended.
  
  exit status 1

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants