Bug #2863

Disable SSL 3.0

Added by fedor.brunner about 4 years ago. Updated over 2 years ago.

Status:ClosedStart date:01/14/2014
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:v14 - Armadillo's Agram
Component:

Description

Hi,
I have checked the SSL behavior in ChatSecure. ChatSecure is currently
supporting SSL3.0 and TLS1.0 for encrypted connections. Because an
active attacker can force ChatSecure to downgrade TLS1.0 to SSL3.0
connection we should disable SSL3.0.

http://crypto.stackexchange.com/questions/10493/why-is-tls-susceptible-to-protocol-downgrade-attacks

According to statistics from
https://xmpp.net/reports.php
TLS 1.0 protocol is supported on 99.5% of public XMPP servers

TLS has a variety of security measures:

  • Protection against a downgrade of the protocol to a previous (less secure) version or a weaker cipher suite.
  • Numbering subsequent Application records with a sequence number and using this sequence number in the message authentication codes (MACs).
  • Using a message digest enhanced with a key (so only a key-holder can check the MAC). The HMAC construction used by most TLS cipher suites is specified in RFC 2104 (SSL 3.0 used a different hash-based MAC).
  • The message that ends the handshake ("Finished") sends a hash of all the exchanged handshake messages seen by both parties.
  • The pseudorandom function splits the input data in half and processes each one with a different hashing algorithm (MD5 and SHA-1), then XORs them together to create the MAC. This provides protection
    even if one of these algorithms is found to be vulnerable.

From a security standpoint, SSL 3.0 should be considered less desirable than TLS 1.0. The SSL 3.0 cipher suites have a weaker key derivation process; half of the master key that is established is
fully dependent on the MD5 hash function, which is not resistant to collisions and is, therefore, not considered secure. Under TLS 1.0, the master key that is established depends on both MD5 and SHA-1 so
its derivation process is not currently considered weak. It is for this reason that SSL 3.0 implementations cannot be validated under FIPS 140-2.

https://en.wikipedia.org/wiki/Transport_Layer_Security

History

#1 Updated by hans about 3 years ago

  • Target version set to v14 - Armadillo's Agram
There is a commit to do this since v14.0.4:

Please test the next release and see if SSLv3 is disabled for you.

#2 Updated by n8fr8 over 2 years ago

  • Status changed from New to Resolved

#3 Updated by n8fr8 over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF