Closed
Bug 1450081
Opened 7 years ago
Closed 5 years ago
"Secure Connection Failed" after installing KB4088879
Categories
(Core :: Security: PSM, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jfarkins, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180323154952
Steps to reproduce:
Using Firefox Quantum version 59.0.2, navigate to https://pmnqatrunkdnsquerytool.popmednet.org/
Actual results:
"Secure Connection Failed" error, page does not load, no Advanced options available
Expected results:
The site should load without error.
NOTE: We are the owner of the destination website and utilize TLS 1.2 ciphers.
Additional information to note:
The website runs on IIS8, on a Windows 2012 R2 Server. After this months Microsoft patching we started to get reports of Firefox users not being able to connect to the website and are receiving a "Secure Connection Failed" error message.
* NOTE, for security reasons, we utilize a subset of ciphers of allowed ciphers instead of the Microsoft default.
I have been able to determine:
- That without the recent KB4088879 patch installed, the Firefox error does NOT occur
- With KB4088879 installed, the Firefox error DOES occur
- With KB4088879 installed, and when I disable our restricted cipher listing, and allow all default ciphers, the Firefox error does NOT occur
- With KB4088879 installed, and when I enable our restricted cipher listing, the Firefox error DOES occur
We are trying to determine:
- What may have caused the sudden change in the cipher behavior
- What are possible solutions to remedy the situation, without enabling all the default ciphers as we find that not the best practice given security vulnerabilities against many of the default ciphers
Comment 1•7 years ago
|
||
I can reproduce this issue on my machine Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Status: UNCONFIRMED → NEW
Component: Untriaged → Security
Ever confirmed: true
Reporter | ||
Comment 2•7 years ago
|
||
Thank you for the feedback. After continued research on my side, I can provide some additional information that is pointing more towards an IIS 8.5/Schannel type of issue. Exactly what, I'm not sure, but other information I've uncovered is as follows:
On the Windows 2012R2 / IIS 8.5 Webserver, the below Schannel errors can be seen in the Event Viewer (System) log:
- An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed.
- A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 1205.
I have also been able to verify that of the 14 cipher suites sent in the Firefox "Client Hello" packet, that 4 of them are in my allowed cipher suite listing:
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
I have also been able to confirm that two other web applications, that don't use IIS, are connecting ok using the same restricted cipher listing. They are in fact connecting ok using cipher suite:
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Which the same cipher suite is not being recognized by IIS/Schannel. My suspicions are growing that this sudden change in behavior is related to an OS change that was made by MS during this most recent patching.
Also to note, I have rolled back the KB4088876 and the KB4088879 patches in my test environment, but am still being presented with this issue.
Thanks for any continued guidance you can provide.
Reporter | ||
Comment 3•7 years ago
|
||
Oops, my apologies, the cipher suite that my two other web applications that don't use IIS are connecting ok on this cipher:
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (*NOT the TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA I mentioned above)
Reporter | ||
Comment 5•7 years ago
|
||
No, a support ticket has not been opened with Microsoft. It appears Microsoft has dropped SChannel support for these two TLS 1.2 RSA cipher suites:
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
These are the only TLS 1.2 RSA cipher suites offered up for authentication by Firefox. Will additional SChannel supported TLS 1.2 RSA cipher suites be added to the cipher suites Firefox can authenticate on? We do not allow SHA1 ciphers due to security requirements. Only TLS 1.2.
Updated•5 years ago
|
Component: Security → Security: PSM
Product: Firefox → Core
![]() |
||
Comment 6•5 years ago
|
||
The site in question works for me.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•