https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 00:56:46 +0000 https://cve.radiocsirt.org/vuln/brew-azure-cli-cve-2024-12797 <p><strong>Affected:</strong> Homebrew: azure-cli</p> <p>pyca/cryptography&#39;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.</p> <p>If you are building cryptography source (&#34;sdist&#34;) 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.</p> <p><strong>Affected:</strong> Homebrew: azure-cli</p> <p>pyca/cryptography&#39;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.</p> <p>If you are building cryptography source (&#34;sdist&#34;) 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.</p> https://cve.radiocsirt.org/vuln/brew-azure-cli-cve-2024-12797 https://cve.radiocsirt.org/vuln/cve-2024-12797 <p><strong>Affected:</strong> OpenSSL</p> <p>Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don&#39;t abort as expected when the SSL_VERIFY_PEER verification mode is set.</p> <p>Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients.</p> <p>RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server&#39;s RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER.</p> <p>Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2.</p> <p>The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.</p> <p><strong>Affected:</strong> OpenSSL</p> <p>Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don&#39;t abort as expected when the SSL_VERIFY_PEER verification mode is set.</p> <p>Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients.</p> <p>RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server&#39;s RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER.</p> <p>Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2.</p> <p>The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.</p> https://cve.radiocsirt.org/vuln/cve-2024-12797 https://cve.radiocsirt.org/vuln/ghsa-79v4-65xg-pq4g <p><strong>Affected:</strong> PyPI: cryptography</p> <p>pyca/cryptography&#39;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.</p> <p>If you are building cryptography source (&#34;sdist&#34;) 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.</p> <p><strong>Affected:</strong> PyPI: cryptography</p> <p>pyca/cryptography&#39;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.</p> <p>If you are building cryptography source (&#34;sdist&#34;) 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.</p> https://cve.radiocsirt.org/vuln/ghsa-79v4-65xg-pq4g