Seguridad: OpenSSL 1.1.0a vulnerable y cómo solucionarlo
Una nueva vulnerabilidad ha sido anunciada por parte de OpenSSL, en el cual advierte de que la actualización de OpenSSL con fecha del 22 de Septiembre:
“This issue only affects OpenSSL 1.1.0a, released on 22nd September 2016.The patch applied to address CVE-2016-6307 resulted in an issue where if a
message larger than approx 16k is received then the underlying buffer to store
the incoming message is reallocated and moved. Unfortunately a dangling pointer
to the old location is left which results in an attempt to write to the
previously freed location. This is likely to result in a crash, however it
could potentially lead to execution of arbitrary code.Reported by Robert Święcki (Google Security Team).”
El usuario Robert Święcki reportó esta falla, a la cual OpenSSL tomó cartas en el asunto para remediar esta solución, en el cual es ocasionado cuando un mensaje sobrepasa el tamaña de aproximadamente 16K; ocasionando un crash en el buffer.
Esta actualización sólo es para aquellas personas que tienen la versión de OpenSSL 1.1.0a, el cual OpenSSL nos recomienda actualizar a la versión 1.1.0b:
Fix Use After Free for large message sizes (CVE-2016-6309) ========================================================== Severity: Critical This issue only affects OpenSSL 1.1.0a, released on 22nd September 2016. The patch applied to address CVE-2016-6307 resulted in an issue where if a message larger than approx 16k is received then the underlying buffer to store the incoming message is reallocated and moved. Unfortunately a dangling pointer to the old location is left which results in an attempt to write to the previously freed location. This is likely to result in a crash, however it could potentially lead to execution of arbitrary code. OpenSSL 1.1.0 users should upgrade to 1.1.0b This issue was reported to OpenSSL on 23rd September 2016 by Robert Święcki (Google Security Team), and was found using honggfuzz. The fix was developed by Matt Caswell of the OpenSSL development team.
Pueden descargar la actualización donde ha sido reparado el inconveniente de seguridad en el siguiente link:
Bytes.
Fuentes: [ CVE | OpenSSL | the register ]
Publicar comentario