It is important to check SSL configuration because sensitive information/data must be secured while transmitting through the network. Transmission of data may include username, password, credit card number, bank account number etc. So it must be protected while transmission or stored. The major type of vulnerabilities occurs when the HTTP protocol transmits sensitive information.
When the SSL/TLS service is present it is good but it increments the attack surface. As with any technology SSL/TLS has its flaws. Below is the list of attacks due to weak SSL/TLS
1) BEAST attack: The Browser Exploit Against SSL/TLS (BEAST) affects SSL3.0 and TLS 1.0. In BEAST attack, an attacker can decrypt data exchanged between two parties by taking advantage of a vulnerability in the implementation of the Cipher Block Chaining (CBC) mode in TLS 1.0 which allows them to perform chosen plaintext attack.
2) POODLE attack: Padding Oracle on Downgraded Legacy Encryption (POODLE) is a man-in-the-middle exploit which takes advantage of Internet and security software clients’ fallback to SSL 3.0
3) CRIME: Compression Ratio Info-leak Made Easy is found in TLS compression. The compression method is included in the ClientHello message and it is optional, meaning that the connection can be established without any compression.
This is a Wireshark capture of a ServerHello message (response to ClientHello), selecting a NULL compression method which means that no compression will be used.
4) BREACH: Browser Reconnaissance and Exfiltration via Adaptive Compression of Hypertext is a method of exploitation which is identical to CRIME, with the exception that BREACH targets HTTP compression whereas CRIME targets TLS compression. This means that TLS compression is not required for this attack to work.
5) HeartBleed: This attack takes advantage of the TLS heartbeat extension which is primarily used as a keep-alive method between two parties to and ensure that the connection is not closed if they are both still there. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names, and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.
It is recommended to select a Certificate Authority (CA) that is reliable. It is also advisable to use secure protocols and strong cipher suites.