Product Affected

This issue affects SRC Series Application Server and Web Administrator versions prior to 4.12.0-R1.
High
7.5 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)

Problem

Multiple vulnerabilities have been resolved in the Juniper Networks Session and Resource Control (SRC) software. The following is a summary of these vulnerabilities and their status:

CVE CVSS Summary
CVE-2011-3389 4.3  (AV:N/AC:M/Au:N/C:P/I:N/A:N) The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.
CVE-2016-2183 7.5 ( CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N ) The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted session, as demonstrated by an HTTPS session using Triple DES in CBC mode, aka a "Sweet32" attack.
 

 

Solution

These issues have been resolved in SRC 4.12.0-R1 and all subsequent releases.

This issue is being tracked as PR  1376101  and  1388384  which are visible on the Customer Support website.
 

Software Releases, patches and updates are available at  https://www.juniper.net/support/downloads/ .
 

Workaround

Use access lists or firewall filters to limit access to the device's management interface only from trusted hosts and administrators.
 

Severity Assessment

Information for how Juniper Networks uses CVSS can be found at KB 16446 [juniper.net] "Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories."

Modification History

2019-01-09: Initial publication

Related Information