A vulnerability has been reported against virtually all versions of OpenSSL stating that client-initiated renegotiation is not properly restricted within the SSL and TLS protocols, which might make it easier for remote attackers to cause a denial of service (CPU consumption) by performing many renegotiations within a single connection. This issue has been assigned CVE-2011-1473 .
The releases listed below will now start a new session when performing renegotiation as a server by using 'SSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION' option in J-Web. All Junos OS software releases built on or after 2013-06-13 have fixed this specific issue. Releases containing the fix specifically include: 10.4S14, 10.4R15, 11.4R7, 12.1R6, 12.1X44-D20 (SRX), 12.2R3, 12.3R2, and all subsequent releases (i.e. all releases built after 12.3R2). Customers can confirm the build date of any Junos OS release by issuing the command 'show version detail'. This issue is being tracked as PR 794253 and is visible on the Customer Support website. A Customer Support login is required. KB16765 [juniper.net] - "In which releases are vulnerabilities fixed?" describes which release vulnerabilities are fixed as per our End of Engineering and End of Life support policies.
How to obtain fixed software: Security vulnerabilities in Junos are fixed in the next available Maintenance Release of each supported Junos version. In some cases, a Maintenance Release is not planned to be available in an appropriate time-frame. For these cases, Service Releases are made available in order to be more timely. Security Advisory and Security Notices will indicate which Maintenance and Service Releases contain fixes for the issues described. Upon request to JTAC, customers will be provided download instructions for a Service Release. Although Juniper does not provide formal Release Note documentation for a Service Release, a list of "PRs fixed" can be provided on request.
Since SSL is used for remote network configuration and management applications such as J-Web and SSL Service for JUNOScript (XNM-SSL), viable workarounds for this issue in Junos include: