POLICY-OTHER --
POLICY-OTHER SSLv2 Client Hello attempt
ssl/s2_srvr.c in OpenSSL 1.0.1 before 1.0.1r and 1.0.2 before 1.0.2f does not prevent use of disabled ciphers, which makes it easier for man-in-the-middle attackers to defeat cryptographic protection mechanisms by performing computations on SSLv2 traffic, related to the get_client_master_key and get_client_hello functions. Impact: CVSS base score 5.9 CVSS impact score 3.6 CVSS exploitability score 2.2 confidentialityImpact HIGH integrityImpact NONE availabilityImpact NONE Details: Ease of Attack:
This rule alerts when an attempt to identify if SSL version 2 is being used by a system.
No public information
No known false positives
Talos research team. This document was generated from data supplied by the national vulnerability database, a product of the national institute of standards and technology. For more information see [nvd].
No rule groups
CVE-2015-3197ssl/s2_srvr.c in OpenSSL 1.0.1 before 1.0.1r and 1.0.2 before 1.0.2f does not prevent use of disabled ciphers, which makes it easier for man-in-the-middle attackers to defeat cryptographic protection mechanisms by performing computations on SSLv2 traffic, related to the get_client_master_key and get_client_hello functions. |
|
|||||||||||||||||||||||||
CVE-2016-0800The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to send a ServerVerify message before establishing that a client possesses certain plaintext RSA data, which makes it easier for remote attackers to decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, aka a "DROWN" attack. |
|
Tactic: Discovery
Technique: Account Discovery
For reference, see the MITRE ATT&CK vulnerability types here: https://attack.mitre.org