0

Half of my users' IE 11.0.9600 browsers suddenly stopped connecting to my older WebLogic (Java) servers. After some digging around, all the users presently unable to connect to these older WL servers have 2 DH ciphers installed:

TLS_DHE_RSA_WITH_AES_128_CBC_SHA  =         0x0033,
TLS_DHE_RSA_WITH_AES_256_CBC_SHA  =         0x0039,

Where could these ciphers possibly have come from? They're not mentioned in any Microsoft documentation, so far as I can find. I see them mentioned in IBM SSL SDKs and Apple Open Source, but I have people with all our IBM stuff installed that don't have these ciphers and I have installed iTunes on a test PC and it didn't install these ciphers. If Microsoft, IBM, and Apple didn't install these on my impacted users' computers, what might have done so?

The presenting issue is not as important to me as the source. The symptom is that these two ciphers appear higher in the cipher order than the next common cipher (AES128 with RSA), so it's selected in the handshake on these machines. The negotiation fails because the older WL servers are sending a 512 bit DH key, and Microsoft SChannel now requires 1024. New WL servers send 1024, and we can fix that. We can also enter the registry key to cause SChannel to accept the 0x0200 (512 bit) key. So, we can fix this point issue easily enough on either end but the mystery is understanding where these ciphers actually came from.

Thanks for any help. I considered submitting this on SuperUser, but figured server-side was more likely to have seen the issue.

  • 2
  • This KB is installed and did not install those 2 ciphers. If the doc for this KB lists these two ciphers, I'm missing it somehow. – codepoke Jan 11 '17 at 18:30
  • It specifically lists those two under "New cipher suites" – Håkan Lindqvist Jan 11 '17 at 18:31
  • I was fooled in looking for the cipher by the fact Microsoft and Fiddler use an inconsistent naming scheme. Fiddler called the cipher TLS_DHE_RSA_WITH_AES_128_SHA while MS calls it TLS_DHE_RSA_WITH_AES_128_CBC_SHA. I found this KB on day one of searching under the Fiddler cipher name, but rejected it because Fiddler did not identify the cert as using CBC. When you linked it from the Apple naming I posted here, I ignored your link because we'd already installed the superseding KB and because I'd already rejected this KB. So, I learned about 10 things here. Thank you, again! – codepoke Jan 12 '17 at 13:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.