A new RFC 7465 has now been published that effectively calls for disabling RC4 everywhere:
o TLS clients MUST NOT include RC4 cipher suites in the ClientHello message. o TLS servers MUST NOT select an RC4 cipher suite when a TLS client sends such a cipher suite in the ClientHello message. o If the TLS client only offers RC4 cipher suites, the TLS server MUST terminate the handshake. The TLS server MAY send the insufficient_security fatal alert in this case.
Cryptographic weaknesses around RC4 were known since many years, but in the beginning of 2013 they finally became feasible to exploit with some considerable, but not too huge of an effort.
The author of the RFC belongs to Microsoft, which published and advisory for disabling RC4 in November 2013 as well. However, Windows Server 2012 R2 with IIS 8.5 which was released in October 2013 still ships with RC4 enabled by default.
A lot of websites and “modern” software still use RC4 today. According to the SSL-Pulse statistics currently more than 60% of all SSL/TLS enabled websites still offer RC4.
It depends on the service and the security requirements, but at the moment I personally don’t see it that much of a problem in offering RC4 as a fallback, if you always prefer other secure ciphers.
Here are some examples of software or websites that still use RC4 in a manner it shouldn’t be used:
- PayPal (server prefers RC4, though offers AES as well)
- Youtube (the servers providing the actual video streams, not the general site;
RC4 exclusively(!))I Tested it last week but it seems like Youtube switched to offering and preferring other AES-based cipher suites just recently.
- All versions of Windows Server and Client OSes, including the respective Internet Explorer enable RC4 by default
- Some VMware products (at least the vCenter Web Client, and many virtual appliances; most seem to prefer AES though; ESXi hosts and vCenter service on port 443 and SSO on 7444 do not support RC4)
- HP ILO interfaces (confirmed with ILO4 2.03, ILO3 1.80; prefers RC4)
- Cisco IronPort Mail appliances seem to be using RC4 exclusively(!)
- Check Point Gaia Portal web interface (tested with R77.20 with JHFA Take 77; RC4 exclusively(!))
Seems like there’s a lot of work waiting for vendors and website admins to disable RC4.
It’s a mystery to me how some popular websites or recent software releases can be released without support for any cipher suite besides RC4. And no, mitigating BEAST is not a valid excuse.