CVE-2017-3737: falha em OpenSSL
Publicada em · Atualizada em
25Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackepss 79%
probabilidade de exploração
79%top 1% das CVEs
exploração observada
nãonenhuma fonte reporta
O que os fabricantes declaram (VEX)
Declarações oficiais dos fabricantes em formato CSAF/VEX: se o produto deles está afetado, já corrigido ou descartado — e por quê. É afirmação do fabricante, não juízo do Vexday.
Red Hatdocumento VEX ↗
Afetado
3 produtos
Red Hat JBoss Enterprise Application Platform 6 · Red Hat JBoss Enterprise Web Server 2 · Red Hat JBoss Web Server 3
no_fix_planned: Will not fix
Corrigido
13 produtos (279 componentes)
Red Hat JBoss Core Services on RHEL 6 Server · Red Hat JBoss Core Services on RHEL 7 Server · Red Hat Enterprise Linux Server (v. 7) · Red Hat Enterprise Linux Server Optional (v. 7) · Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7) · e outros 8
Não afetado
7 produtos (23 componentes) — porque o código vulnerável não está presente no produto
Red Hat Enterprise Linux 6 · Red Hat Enterprise Linux 8 · Red Hat Enterprise Linux 7 · Red Hat Enterprise Virtualization 3 · Red Hat Enterprise Linux 5 · e outros 2
OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism. The intent was that if a fatal error occurred during a handshake then OpenSSL would move into the error state and would immediately fail if you attempted to continue the handshake. This works as designed for the explicit handshake functions (SSL_do_handshake(), SSL_accept() and SSL_connect()), however due to a bug it does not work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is subsequently called by the application for the same SSL object then it will succeed and the data is passed without being decrypted/encrypted directly from the SSL/TLS record layer. In order to exploit this issue an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued after having already received a fatal error. OpenSSL version 1.0.2b-1.0.2m are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is not affected.
Produtos afetados
OpenSSL Software Foundation · OpenSSLCVEs relacionadas — OpenSSL
No mesmo produto, das mais perigosas para as menos.
Referências
https://access.redhat.com/errata/RHSA-2018:0998https://access.redhat.com/errata/RHSA-2018:2185https://access.redhat.com/errata/RHSA-2018:2186https://access.redhat.com/errata/RHSA-2018:2187https://cert-portal.siemens.com/productcert/pdf/ssa-179516.pdfhttps://github.com/openssl/openssl/commit/898fb884b706aaeb283de4812340bb0bde8476dchttps://security.FreeBSD.org/advisories/FreeBSD-SA-17:12.openssl.aschttps://security.gentoo.org/glsa/201712-03https://security.netapp.com/advisory/ntap-20171208-0001/https://security.netapp.com/advisory/ntap-20180117-0002/https://security.netapp.com/advisory/ntap-20180419-0002/https://www.debian.org/security/2017/dsa-4065