Bug 36171 - nss: SSL3 protocol attack (3.2)
nss: SSL3 protocol attack (3.2)
Status: CLOSED WORKSFORME
Product: UCS
Classification: Unclassified
Component: Security updates
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.2-x-errata
Assigned To: Security maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-15 10:40 CEST by Moritz Muehlenhoff
Modified: 2019-04-11 19:24 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2014-10-15 10:40:03 CEST
+++ This bug was initially created as a clone of Bug #36170 +++

CVE-2014-3566

This will requires fixes in openssl, gnutls and nss. Firefox also needs a fix since it uses a local nss copy. (There are additional Firefox issues, so I'll file a separate bug).

http://googleonlinesecurity.blogspot.fr/2014/10/this-poodle-bites-exploiting-ssl-30.html
https://www.openssl.org/~bodo/ssl-poodle.pdf
Comment 1 Moritz Muehlenhoff univentionstaff 2014-10-30 13:02:12 CET
An implementation of SCSV isn't available yet, resetting target milestone
Comment 2 Moritz Muehlenhoff univentionstaff 2014-12-09 15:12:32 CET
NSS upstream won't change it; as long as a client like uses a secure protocol version like TLS 1.x, setups are secure.