Update dependency cryptography to v43 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
cryptography (changelog)	==39.0.1 → ==43.0.1

---

Vulnerable OpenSSL included in cryptography wheels

GHSA-39hc-v87j-747x

More information

Details

pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 37.0.0-38.0.3 are vulnerable to a number of security issues. More details about the vulnerabilities themselves can be found in https://www.openssl.org/news/secadv/20221101.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.

Severity

Medium

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-39hc-v87j-747x
• https://github.com/pyca/cryptography/commit/382e759bcded5773330eeed748c86b213ec618c5
• https://github.com/pyca/cryptography/commit/cf2ada625d1188d6cd46396f301b98095da577f7
• https://github.com/advisories/GHSA-39hc-v87j-747x

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Cipher.update_into can corrupt memory if passed an immutable python object as the outbuf

CVE-2023-23931 / GHSA-w7pp-m8wf-vj6r

More information

Details

Previously, Cipher.update_into would accept Python objects which implement the buffer protocol, but provide only immutable buffers:

>>> outbuf = b"\x00" * 32
>>> c = ciphers.Cipher(AES(b"\x00" * 32), modes.ECB()).encryptor()
>>> c.update_into(b"\x00" * 16, outbuf)
16
>>> outbuf
b'\xdc\x95\xc0x\xa2@​\x89\x89\xadH\xa2\x14\x92\x84 \x87\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'

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.

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-w7pp-m8wf-vj6r
• https://nvd.nist.gov/vuln/detail/CVE-2023-23931
• https://github.com/pyca/cryptography/commit/d6951dca25de45abd52da51b608055371fbcde4e
• https://github.com/pyca/cryptography/pull/8230
• https://github.com/pypa/advisory-database/tree/main/vulns/cryptography/PYSEC-2023-11.yaml
• https://lists.debian.org/debian-lts-announce/2024/10/msg00012.html
• https://security.netapp.com/advisory/ntap-20230324-0007
• https://github.com/advisories/GHSA-w7pp-m8wf-vj6r

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Vulnerable OpenSSL included in cryptography wheels

CVE-2023-0286 / GHSA-x4qr-2fvf-3mr5

More information

Details

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.

Severity

• CVSS Score: 7.4 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-x4qr-2fvf-3mr5
• https://nvd.nist.gov/vuln/detail/CVE-2023-0286
• https://rustsec.org/advisories/RUSTSEC-2023-0006.html
• https://www.openssl.org/news/secadv/20230207.txt
• https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2c6c9d439b484e1ba9830d8454a34fa4f80fdfe9
• https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2f7530077e0ef79d98718138716bc51ca0cad658
• https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fd2af07dc083a350c959147097003a14a5e8ac4d
• https://access.redhat.com/security/cve/cve-2023-0286
• https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-3.6.2-relnotes.txt
• https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/018_x509.patch.sig
• https://security.gentoo.org/glsa/202402-08
• https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003
• https://github.com/advisories/GHSA-x4qr-2fvf-3mr5

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Vulnerable OpenSSL included in cryptography wheels

GHSA-5cpq-8wj7-hf2v

More information

Details

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.

Severity

Low

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-5cpq-8wj7-hf2v
• https://github.com/pyca/cryptography/commit/8708245ccdeaff21d65eea68a4f8d2a7c5949a22
• https://cryptography.io/en/latest/changelog/#v41-0-0
• https://github.com/advisories/GHSA-5cpq-8wj7-hf2v

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

pyca/cryptography's wheels include vulnerable OpenSSL

GHSA-jm77-qphf-c4w8

More information

Details

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.

Severity

Low

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-jm77-qphf-c4w8
• https://github.com/pyca/cryptography/commit/b22271cf3c3dd8dc8978f8f4b00b5c7060b6538d
• https://github.com/pyca/cryptography/commit/bfa4d95f0f356f2d535efd5c775e0fb3efe90ef2
• https://www.openssl.org/news/secadv/20230714.txt
• https://www.openssl.org/news/secadv/20230719.txt
• https://www.openssl.org/news/secadv/20230731.txt
• https://github.com/advisories/GHSA-jm77-qphf-c4w8

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Vulnerable OpenSSL included in cryptography wheels

GHSA-v8gr-m533-ghj9

More information

Details

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.

Severity

Low

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-v8gr-m533-ghj9
• https://github.com/pyca/cryptography/commit/fc11bce6930e591ce26a2317b31b9ce2b3e25512
• https://github.com/advisories/GHSA-v8gr-m533-ghj9

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

cryptography vulnerable to NULL-dereference when loading PKCS7 certificates

CVE-2023-49083 / GHSA-jfhm-5ghh-2f97

More information

Details

Summary

Calling load_pem_pkcs7_certificates or load_der_pkcs7_certificates could lead to a NULL-pointer dereference and segfault.

PoC

Here is a Python code that triggers the issue:

from cryptography.hazmat.primitives.serialization.pkcs7 import load_der_pkcs7_certificates, load_pem_pkcs7_certificates

pem_p7 = b"""
-----BEGIN PKCS7-----
MAsGCSqGSIb3DQEHAg==
-----END PKCS7-----
"""

der_p7 = b"\x30\x0B\x06\x09\x2A\x86\x48\x86\xF7\x0D\x01\x07\x02"

load_pem_pkcs7_certificates(pem_p7)
load_der_pkcs7_certificates(der_p7)

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.

Severity

• CVSS Score: 5.9 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-jfhm-5ghh-2f97
• https://github.com/pyca/cryptography/commit/f09c261ca10a31fe41b1262306db7f8f1da0e48a
• https://nvd.nist.gov/vuln/detail/CVE-2023-49083
• https://github.com/pyca/cryptography/pull/9926
• http://www.openwall.com/lists/oss-security/2023/11/29/2
• https://github.com/pypa/advisory-database/tree/main/vulns/cryptography/PYSEC-2023-254.yaml
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QMNTYMUGFJSDBYBU22FUYBHFRZODRKXV
• https://lists.debian.org/debian-lts-announce/2024/10/msg00012.html
• https://github.com/advisories/GHSA-jfhm-5ghh-2f97

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Python Cryptography package vulnerable to Bleichenbacher timing oracle attack

CVE-2023-50782 / GHSA-3ww4-gg4f-jr7f

More information

Details

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.

Severity

• CVSS Score: 8.7 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

References

• https://nvd.nist.gov/vuln/detail/CVE-2023-50782
• https://access.redhat.com/security/cve/CVE-2023-50782
• https://bugzilla.redhat.com/show_bug.cgi?id=2254432
• https://github.com/pyca/cryptography/issues/9785
• https://www.couchbase.com/alerts
• https://github.com/advisories/GHSA-3ww4-gg4f-jr7f

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Null pointer dereference in PKCS12 parsing

CVE-2024-0727 / GHSA-9v9h-cgj8-h64p

More information

Details

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.

Severity

• CVSS Score: 5.5 / 10 (Medium)
• Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

References

• https://nvd.nist.gov/vuln/detail/CVE-2024-0727
• https://github.com/openssl/openssl/commit/09df4395b5071217b76dc7d3d2e630eb8c5a79c2
• https://github.com/openssl/openssl/commit/775acfdbd0c6af9ac855f34969cdab0c0c90844a
• https://github.com/openssl/openssl/commit/d135eeab8a5dbf72b3da5240bab9ddb7678dbd2c
• https://github.openssl.org/openssl/extended-releases/commit/03b3941d60c4bce58fab69a0c22377ab439bc0e8
• https://github.openssl.org/openssl/extended-releases/commit/aebaa5883e31122b404e450732dc833dc9dee539
• https://www.openssl.org/news/secadv/20240125.txt
• https://github.com/github/advisory-database/pull/3472
• https://github.com/openssl/openssl/pull/23362
• https://github.com/alexcrichton/openssl-src-rs/commit/add20f73b6b42be7451af2e1044d4e0e778992b2
• https://github.com/pyca/cryptography/commit/3519591d255d4506fbcd0d04037d45271903c64d
• https://security.netapp.com/advisory/ntap-20240208-0006
• http://www.openwall.com/lists/oss-security/2024/03/11/1
• https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
• https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
• https://github.com/advisories/GHSA-9v9h-cgj8-h64p

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

cryptography NULL pointer dereference with pkcs12.serialize_key_and_certificates when called with a non-matching certificate and private key and an hmac_hash override

CVE-2024-26130 / GHSA-6vqw-3v5j-54x4

More information

Details

If pkcs12.serialize_key_and_certificates is called with both:

1. A certificate whose public key did not match the provided private key
2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

Then a NULL pointer dereference would occur, crashing the Python process.

This has been resolved, and now a ValueError is properly raised.

Patched in https://github.com/pyca/cryptography/pull/10423

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-6vqw-3v5j-54x4
• https://github.com/pyca/cryptography/pull/10423
• https://github.com/pyca/cryptography/commit/97d231672763cdb5959a3b191e692a362f1b9e55
• https://nvd.nist.gov/vuln/detail/CVE-2024-26130
• https://github.com/pypa/advisory-database/tree/main/vulns/cryptography/PYSEC-2024-225.yaml
• https://github.com/advisories/GHSA-6vqw-3v5j-54x4

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

pyca/cryptography has a vulnerable OpenSSL included in cryptography wheels

GHSA-h4gh-qq45-vh27

More information

Details

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.

Severity

Medium

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-h4gh-qq45-vh27
• https://openssl-library.org/news/secadv/20240903.txt
• https://github.com/advisories/GHSA-h4gh-qq45-vh27

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

pyca/cryptography (cryptography)

v43.0.1

Compare Source

v43.0.0

Compare Source

v42.0.8

Compare Source

v42.0.7

Compare Source

v42.0.6

Compare Source

v42.0.5

Compare Source

v42.0.4

Compare Source

v42.0.3

Compare Source

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• 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.