-
Notifications
You must be signed in to change notification settings - Fork 17
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
chore(deps): update dependency cryptography to v42 [security] #5358
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/pypi-cryptography-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
November 30, 2023 05:26
5ed174c
to
b88ca87
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
2 times, most recently
from
February 6, 2024 04:54
2f1555e
to
dde482b
Compare
renovate
bot
changed the title
chore(deps): update dependency cryptography to v41 [security]
chore(deps): update dependency cryptography to v42 [security]
Feb 6, 2024
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
February 6, 2024 16:16
dde482b
to
70026b6
Compare
renovate
bot
changed the title
chore(deps): update dependency cryptography to v42 [security]
Update dependency cryptography to v42 [SECURITY]
Feb 6, 2024
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
February 17, 2024 02:37
70026b6
to
db0470d
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
3 times, most recently
from
March 6, 2024 13:53
f597c11
to
c6fa12f
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
2 times, most recently
from
March 26, 2024 12:43
009deb1
to
a7cc973
Compare
renovate
bot
changed the title
Update dependency cryptography to v42 [SECURITY]
chore(deps): update dependency cryptography to v42 [security]
Mar 26, 2024
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
March 26, 2024 14:37
a7cc973
to
c6f11ed
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
April 2, 2024 15:06
c6f11ed
to
f835525
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
2 times, most recently
from
April 17, 2024 12:03
6ccc5c1
to
c634b8f
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
4 times, most recently
from
April 25, 2024 18:07
d60b202
to
7f4fbbe
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
May 3, 2024 15:46
7f4fbbe
to
c5b222b
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
2 times, most recently
from
May 20, 2024 19:53
49d4e5f
to
84ffc3f
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
May 28, 2024 20:06
84ffc3f
to
8ed72af
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
2 times, most recently
from
June 17, 2024 15:12
d0ba9a0
to
d28ab6b
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
3 times, most recently
from
October 7, 2024 19:19
df47cb4
to
95a550e
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
October 17, 2024 14:05
95a550e
to
233868a
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
October 25, 2024 12:21
233868a
to
edea8b5
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
3 times, most recently
from
November 25, 2024 15:53
0078366
to
dcb468e
Compare
renovate
bot
changed the title
chore(deps): update dependency cryptography to v42 [security]
chore(deps): update dependency cryptography to v42 [security] - autoclosed
Dec 6, 2024
renovate
bot
changed the title
chore(deps): update dependency cryptography to v42 [security] - autoclosed
chore(deps): update dependency cryptography to v42 [security]
Dec 9, 2024
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
3 times, most recently
from
December 10, 2024 01:09
f66d7c7
to
72dfbe3
Compare
renovate
bot
force-pushed
the
renovate/pypi-cryptography-vulnerability
branch
from
December 10, 2024 19:05
72dfbe3
to
a9f38af
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.3.2
->==42.0.2
GitHub Vulnerability Alerts
CVE-2023-23931
Previously,
Cipher.update_into
would accept Python objects which implement the buffer protocol, but provide only immutable buffers:This would allow immutable objects (such as
bytes
) to be mutated, thus violating fundamental rules of Python. This is a soundness bug -- it allows programmers to misuse an API, it cannot be exploited by attacker controlled data alone.This now correctly raises an exception.
This issue has been present since
update_into
was originally introduced in cryptography 1.8.CVE-2023-0286
pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 0.8.1-39.0.0 are vulnerable to a security issue. More details about the vulnerabilities themselves can be found in https://www.openssl.org/news/secadv/20221213.txt and https://www.openssl.org/news/secadv/20230207.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.
GHSA-5cpq-8wj7-hf2v
pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 0.5-40.0.2 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://www.openssl.org/news/secadv/20230530.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.
GHSA-jm77-qphf-c4w8
pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 0.8-41.0.2 are vulnerable to several security issues. More details about the vulnerabilities themselves can be found in https://www.openssl.org/news/secadv/20230731.txt, https://www.openssl.org/news/secadv/20230719.txt, and https://www.openssl.org/news/secadv/20230714.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.
GHSA-v8gr-m533-ghj9
pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 2.5-41.0.3 are vulnerable to several security issues. More details about the vulnerabilities themselves can be found in https://www.openssl.org/news/secadv/20230908.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-2023-49083
Summary
Calling
load_pem_pkcs7_certificates
orload_der_pkcs7_certificates
could lead to a NULL-pointer dereference and segfault.PoC
Here is a Python code that triggers the issue:
Impact
Exploitation of this vulnerability poses a serious risk of Denial of Service (DoS) for any application attempting to deserialize a PKCS7 blob/certificate. The consequences extend to potential disruptions in system availability and stability.
CVE-2023-50782
A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.
CVE-2024-0727
Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL
to crash leading to a potential Denial of Service attack
Impact summary: Applications loading files in the PKCS12 format from untrusted
sources might terminate abruptly.
A file in PKCS12 format can contain certificates and keys and may come from an
untrusted source. The PKCS12 specification allows certain fields to be NULL, but
OpenSSL does not correctly check for this case. This can lead to a NULL pointer
dereference that results in OpenSSL crashing. If an application processes PKCS12
files from an untrusted source using the OpenSSL APIs then that application will
be vulnerable to this issue.
OpenSSL APIs that are vulnerable to this are: PKCS12_parse(),
PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes()
and PKCS12_newpass().
We have also fixed a similar issue in SMIME_write_PKCS7(). However since this
function is related to writing data we do not consider it security significant.
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.
Release Notes
pyca/cryptography (cryptography)
v42.0.2
Compare Source
v42.0.1
Compare Source
v42.0.0
Compare Source
v41.0.7
Compare Source
v41.0.6
Compare Source
v41.0.5
Compare Source
v41.0.4
Compare Source
v41.0.3
Compare Source
v41.0.2
Compare Source
v41.0.1
Compare Source
v41.0.0
Compare Source
v40.0.2
Compare Source
v40.0.1
Compare Source
v40.0.0
Compare Source
v39.0.2
Compare Source
v39.0.1
Compare Source
v39.0.0
Compare Source
v38.0.4
Compare Source
v38.0.3
Compare Source
v38.0.2
Compare Source
v38.0.1
Compare Source
v38.0.0
Compare Source
v37.0.4
Compare Source
v37.0.3
Compare Source
v37.0.2
Compare Source
v37.0.1
Compare Source
v37.0.0
Compare Source
v36.0.2
Compare Source
v36.0.1
Compare Source
v36.0.0
Compare Source
v35.0.0
Compare Source
v3.4.8
Compare Source
v3.4.7
Compare Source
v3.4.6
Compare Source
v3.4.5
Compare Source
v3.4.4
Compare Source
v3.4.3
Compare Source
v3.4.2
Compare Source
v3.4.1
Compare Source
v3.4
Compare Source
Configuration
📅 Schedule: Branch creation - "" in timezone US/Eastern, 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.