Insecure Transport: Weak SSL Protocol

Summary

The Transport Layer Security (TLS) protocol provides a protection mechanism to better protect authenticity, confidentiality and integrity of the data transmitted between a client and a web server. The TLS protocol has undergone various revisions resulting in periodic version updates. Each revision tries to address security weakness in prior versions and incorporate support for the latest in security measures. It is strongly recommended to use the latest version of the available protocol, whenever possible.

TLS 1.0 is considered insecure as it lacks support for strong ciphersuites and is known to be plagued by several known vulnerabilities. It either uses RC4 cipher, which is prone to bias attacks or uses Cipher Block Chaining (CBC) mode cipher, which enables condition for POODLE (Padding Oracle OnDowngraded Legacy Encryption) attacks.

NIST Special Publication 800-52 Revision 1 no longer considers TLS 1.0 as strong cryptography. TLS 1.0 is also no longer in compliance with PCI DSS v3.1 requirements. PCI does not consider TLS 1.0 to be adequate to protect cardholder data and has deprecated its use starting June 2016.

Update: PCI DSS has extended deadline for migration to TLS1.1 or above to June 30, 2018.

However, an early migration is recommended to ensure security of your data and applications.


Use of insecure protocol versions will weaken the strength of the transport protection and could allow an attacker to compromise, steal or modify sensitive information. Configuring the web server to use the most secure protocol, TLS 1.1 or TLS 1.2 is highly recommended.

Explanation

Use of a weak protocol such as TLS 1.0 leaves the connection vulnerable to man-in-the-middle attacks. This would allow the attacker to read and modify data on a secure TLS connection, thus compromising user security and privacy. Its use would also limit the use of strong cipher suites that help protect data integrity and confidentiality.

Recommendation

Disable support for the TLS 1.0 protocol on the server. Both NIST 800-52 and PCI DSS v3.1 strongly

recommend upgrade to the latest version of TLS available, TLS 1.2. Or, at a minimum an upgrade to TLS 1.1.


For Apache, modify the following lines in the server configuration

SSLProtocol ALL –SSLv2 -SSLv3 -TLSv1

For Nginx, modify the following lines in server configuration:

ssl_protocols TLSv1.1 TLSv1.2;

For IIS, please refer to Microsoft Knowledge Base Articles:

https://technet.microsoft.com/library/security/3009008

For other servers, please refer to vendor specific documentation.


OWASP

https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Protection_Cheat_Sheet.html


NIST

http://www.nist.gov/customcf/get_pdf.cfm?pub_id=915856


PCI Security Standards Council:


https://www.pcisecuritystandards.org/documents/Migrating_from_SSL_Early_TLS_Information%20Supplement_v1.pdf

https://www.pcisecuritystandards.org/pdfs/15_03_25_PCI_SSC_FAQ_SSL_Protocol_Vulnerability_Revisions_to_PCI_DSS_PAD.pdf


Microsoft

https://support.microsoft.com/en-us/help/187498/how-to-disable-pct-1-0-ssl-2-0-ssl-3-0-or-tls-1-0-in-internet-informat

http://support.microsoft.com/kb/245030/

https://support.microsoft.com/en-us/help/245030/how-to-restrict-the-use-of-certain-cryptographic-algorithms-and-protoc


Apache

http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html

CVE-2014-8730


POODLE Vulnerability Expands Beyond SSLv3 to TLS 1.0 and 1.1

https://www.globalsign.com/en/blog/poodle-vulnerability-expands-beyond-sslv3-to-tls/

TLS Fallback Signaling Cipher Suite Value (SCSV) for Preventing Protocol Downgrade

Attacks

https://tools.ietf.org/html/draft-ietf-tls-downgrade-scsv-00l

Comments

Popular posts from this blog

Insecure Transport - Weak SSL Cipher

List of HTTP status codes

Insecure Transport: Channel Mixing