cuberite/polarssl
1
0
Fork 0
mirror of https://github.com/cuberite/polarssl.git synced 2025-10-03 18:43:38 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1279 from gilles-peskine-arm/memory_allocation_cleanup_psa_crypto_rsa-changelog-3.6

Browse Source 
Backport 3.6: Changelog entry for the RSA memory leak (+ extra changelog fixes)
This commit is contained in:
David Horstmann 2024-08-22 15:45:07 +01:00 committed by GitHub
commit d8d5353218
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog.d/fix_reporting_of_key_usage_issues.txt
View File

@ -1,9 +1,9 @@
Security Security
* With TLS 1.3, when a server enables optional authentication of the * With TLS 1.3, when a server enables optional authentication of the
client, if the client-provided certificate does not have appropriate values client, if the client-provided certificate does not have appropriate values
in if keyUsage or extKeyUsage extensions, then the return value of in keyUsage or extKeyUsage extensions, then the return value of
mbedtls_ssl_get_verify_result() would incorrectly have the mbedtls_ssl_get_verify_result() would incorrectly have the
MBEDTLS_X509_BADCERT_KEY_USAGE and MBEDTLS_X509_BADCERT_KEY_USAGE bits MBEDTLS_X509_BADCERT_KEY_USAGE and MBEDTLS_X509_BADCERT_EXT_KEY_USAGE bits
clear. As a result, an attacker that had a certificate valid for uses other clear. As a result, an attacker that had a certificate valid for uses other
than TLS client authentication could be able to use it for TLS client than TLS client authentication could be able to use it for TLS client
authentication anyway. Only TLS 1.3 servers were affected, and only with authentication anyway. Only TLS 1.3 servers were affected, and only with

3
ChangeLog.d/mbedtls_psa_rsa_load_representation-memory_leak.txt Normal file
View File

@ -0,0 +1,3 @@
Bugfix
* Fix a memory leak that could occur when failing to process an RSA
key through some PSA functions due to low memory conditions.