polarssl: security bump to version 1.2.18
PATCH 1/1 polarssl: security bump to version 1.2.18
Fixes a potential heap corruption on Windows when mbedtls_x509_crt_parse_path() is passed a path longer than 2GB. This cannot be triggered remotely. Found by Guido Vranken, Intelworks.
Fixes a potential buffer overflow in some asn1_write_xxx() functions. This cannot be triggered remotely unless you create X.509 certificates based on untrusted input or write keys of untrusted origin. Found by Guido Vranken, Intelworks.
The X509 max_pathlen constraint was not enforced on intermediate certificates. Found by Nicholas Wilson, and fix and tests provided by Janos Follath.
--- package/polarssl/polarssl.hash | 4 ++-- package/polarssl/polarssl.mk | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
package/polarssl/polarssl.hash +2 -2
@@ -1,2 +1,2 @@ -# From https://tls.mbed.org/tech-updates/releases/mbedtls-2.1.2-and-1.3.14-and-polarssl-1.2.17-released -sha256 9301d4ebec3eb45bc9f28f2d79bfdb0c3dd351c386aa6cc66643e1b2be274d52 polarssl-1.2.17-gpl.tgz +# From https://tls.mbed.org/tech-updates/releases/mbedtls-2.2.0-2.1.3-1.3.15-and-polarssl.1.2.18-released +sha256 63c4ed4d9f6a241088e2287958f265403f874248d6a98b98f27cd3aa2f90f030 polarssl-1.2.18-gpl.tgz
package/polarssl/polarssl.mk +1 -1
@@ -5,7 +5,7 @@ ################################################################################ POLARSSL_SITE = https://tls.mbed.org/code/releases -POLARSSL_VERSION = 1.2.17 +POLARSSL_VERSION = 1.2.18 POLARSSL_SOURCE = polarssl-$(POLARSSL_VERSION)-gpl.tgz POLARSSL_CONF_OPTS = \ -DENABLE_PROGRAMS=$(if $(BR2_PACKAGE_POLARSSL_PROGRAMS),ON,OFF)
Signature · 1 line
2.4.10
PATCH 1/1 polarssl: security bump to version 1.2.18
Quoted 11 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Gustavo" == Gustavo Zacarias <[email protected]> writes:
Fixes a potential heap corruption on Windows when
mbedtls_x509_crt_parse_path()is passed a path longer than 2GB. This cannot be triggered remotely. Found by Guido Vranken, Intelworks.Fixes a potential buffer overflow in some
asn1_write_xxx()functions. This cannot be triggered remotely unless you create X.509 certificates based on untrusted input or write keys of untrusted origin. Found by Guido Vranken, Intelworks.
Quoted 5 lines
The X509
max_pathlenconstraint was not enforced on intermediate certificates. Found by Nicholas Wilson, and fix and tests provided by Janos Follath.Signed-off-by Gustavo Zacarias <[email protected]>
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard