Firefox claims to support TLS_ECDHE_RSA_AES_GCM_SHA256 and TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 even in TLS 1.0

VERIFIED FIXED in Firefox 27



Security: PSM
4 years ago
4 years ago


(Reporter: briansmith, Assigned: cviecco)


Dependency tree / graph

Firefox Tracking Flags

(firefox27+ verified)



(2 attachments)

+++ This bug was initially created as a clone of Bug #916226 +++

We need to back out the patch for bug 916226 until the patch for bug 919677 lands in mozilla-central.
status-firefox26: --- → affected
status-firefox27: --- → affected
tracking-firefox26: --- → ?
tracking-firefox27: --- → ?
tracking-firefox26: ? → +
tracking-firefox27: ? → +


4 years ago
Depends on: 912155
Why does this depend on bug 912155? It would be better to back out the patch now, especially from m-a and m-b, because I think bug 912155 is likely to take a while to go through review, etc.
Flags: needinfo?(cviecco)

Comment 2

4 years ago
my bad.. bad bug.
No longer depends on: 912155
Flags: needinfo?(cviecco)

Comment 3

4 years ago
Created attachment 816759 [details] [diff] [review]


4 years ago
Attachment #816759 - Flags: review?(brian)
Attachment #816759 - Flags: review?(brian) → review+
Last Resolved: 4 years ago
status-firefox27: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
Blocks: 926773

Comment 5

4 years ago
Comment on attachment 816759 [details] [diff] [review]

[Approval Request Comment]
Bug caused by (feature/regressing bug #): 
The landing of  916226 exposed bug 919677 in where the servers might get confused by the choice of ciphersuites.
User impact if declined: 
Some servers might get confused if they partially understand TLS 1.2 and attempt to negotiate TLS1.2 ciphers on the TLS1.0 connections. Some sites might be unreachable.

Testing completed (on m-c, etc.): 
landed on m-c and runs with default settings do no expose the new ciphersuites. Leaving the exact behavior as on FF 25. 

Risk to taking this patch (and alternatives if risky): 
None come to mind.

String or IDL/UUID changes made by this patch:
Attachment #816759 - Flags: approval-mozilla-aurora?
Attachment #816759 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+

Comment 6

4 years ago
lsblack thanks for the approbal, but ryanvm backed out 916226 ( yesterday night and this this patch is no longer needed on aurora.

Comment 7

4 years ago
There is no need for tracking for ff26 as ryanvm backed out the prereq and thus this fix is no longer needed


4 years ago
Keywords: verifyme


4 years ago
status-firefox26: affected → ---
tracking-firefox26: + → ---
Is there any help needed for manual testing here? If yes can you please provide some steps in order to reproduce/verify this?
Flags: needinfo?(cviecco)

Comment 9

4 years ago
This is unfriendly.. but here it is:
1. Install tcpdump + wireshark on your local machine
2. Select a host (with a unique ip) that supports https 
3. Start tcpdump collection for that ip saving collection to a file
4. Start firefox, change the security.tls.max.version (ensure that secuiry.tls.max.version is 1 (TLS 1.0).
5. Connect via https to the host you selected 
6. stop firefox
7. Stop your collector
8. open wireshark with the file collected via tcpdmump
9. Inside the the client-hello message (should be the first data package from the dump (4th package in the conversiation) look inse the SSL->TLS v1.0 record layer-> handhsake protocol: Client Hello -> Cipher suites. The AES GCM ciphers should not be listed.

You could do the colletion inside wireshark directly, but that could be unsafe.
Flags: needinfo?(cviecco)
Created attachment 828590 [details]
tcpdump testing log

Thanks Camilo for helping, I was able to reproduce the issue on a older nightly build (AES GCM ciphers appear there), on latest Aurora 27.0a2 I am not seeing listed any AES GCM ciphers. Here is the log file received from tcpdump. 
Based on this I`m setting this verified as fixed.
status-firefox27: fixed → verified
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.