Wednesday, 16 March 2016

Dynamic-VPN connections from Pulse Secure clients fail to establish HTTP connections to SRX devices

SRX-Branch devices running Junos versions 12.1X44-D55, 12.1X46-D40, 12.1X47-D30, or 12.3X48-D20  fail to establish the initial HTTP communications from Pulse Secure clients resulting in failed VPN connections.

During failed connections the Pulse Secure client will display the following connection failures:
    

During failed connections, SRX devices will log a failure in /var/log/httpd.log with the following message.

httpd: 2: Error: "Not Found", code 404 for URI "/junos-auth/", file "/html/junos-auth": Can't open document: /html/junos-auth.
httpd: 2: redirectCallback /junos-auth/
httpd: 2: GET /servererror.php?code=404 HTTP/1.1

This issue is being tracked by PR 1135780.
Solution:
Junos maintenance releases with correction:
  • Junos 12.1X44-D60
  • Junos 12.1X46-D45
  • Junos 12.1X47-D35
  • Junos 12.3X48-D25

Thursday, 10 March 2016

Software Release Notification: Junos OS 13.3R9

Alert Type:

SRN - Software Release Notification
Product Affected:
M-series, MX-series, T-series, PTX-series, EX-Series
Alert Description:
Junos OS 13.3R9 is now available.

Solution:

Consult Release Notes:

For new and changed features, changes in behavior, known behavior and issues, resolved issues, and more.

Download Junos OS Software:
1. Go to Junos Platforms - Download Software page.
2. Select your product.
3. Under 'Version' on the right, select your version.
4. Click the "Software" tab.
5. Select the Install Package Release needed, and follow the prompts.

Saturday, 20 February 2016

Junos OS Release Numbers

The Junos OS release number represents a particular revision of the software that runs on a Juniper Networks routing platform, for example, Junos OS Release 8.5, 9.1, or 9.2. Each Junos OS release has certain new features that complement the software processes that support Internet routing protocols, control the device’s interfaces and the device chassis itself, and allow device system management. On the Juniper Networks Support Web page, you download Junos OS for a particular Junos OS release number.
The following example shows how the software release number is formatted:
m.nZb.s

For example:
9.2R1.8

Where:
  • m is the major release number of the product
  • n is the minor release number of the product
  • Z is the type of software release. The following release types are used:
    • R—FRS/Maintenance release software
    • B—Beta release software
    • I—Internal release software: Private software release for verifying fixes
    • S—Service release software: Released to customers to solve a specific problem—this release will be maintained along with the life span of the underlying release
    • X—Special (eXception) release software: Released to customers to solve an immediate problem—customers are expected to migrate to a supported release when available
  • b is the build number of the product
    • if b=1: Software is the FRS release
    • if b>1: Software is a maintenance release
  • s is the spin number of the product

Sunday, 7 February 2016

NorthStar Controller

 Features:

  • Provides complex interdomain path computation and network optimization services.
  • Employs sophisticated, industry-leading path computation algorithms.
  • Addresses multilayer optimization with multiple user-defined constraints.
  • Provides specific ordering and synchronization of paths that are signaled across routed network elements.
  • Offers a global view of network state for monitoring, management, and proactive planning.
  • Features predictable, deterministic network state within a margin of error for demand forecasts.
  • Minimizes distributed state and increases efficiency of existing network elements by offloading control-plane processing.
  • Creates a foundation for additional centralized network infrastructure services through an API for the network.
  • Simplifies operations by enabling SDN programmability control points across disparate network elements.

Monday, 18 January 2016

JTAC recommended versions of Junos software

TAC recommended versions of Junos software are listed to assist with determining which version of software to download and install.
This article applies to the following devices:
  • SRX Series
Problem or Goal:
For customers planning an upgrade or initial installation, JTAC recommends the Junos software versions in this article. These versions are selected using input from Juniper Engineering, customers, and analysis of field usage data.

Exceptions to this include:
  • JTAC has specifically recommended that customers use a version of Junos software that is different from what is listed.
  • You require specific features that are available only in another version of Junos software. In this case, be sure to download the latest maintenance release.
  • Your currently installed version of Junos is working well.
  • If you use NSM, refer to the NSM & Junos Compatibility Matrix to make sure the recommended Junos software version can be managed by NSM.

Solution:
To download Junos Software, go to the Junos Platforms - Download Software site.
The JTAC Recommended Junos Releases are in the tables below.

SRX Series Services Gateways

Platform JTAC Recommended Junos Software by Platform Release
Type
Last
Updated
vSRX Junos 15.1X49-D15.4 Standard 04 Sep 2015
SRX100B/H Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX100H2 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX110H Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX110H2 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX210B/H/BE/HE Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX210H2 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX220H Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX220H2 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX240B/H/B2/H2 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX550 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX650 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX1400 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX3400 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX3600 Junos 12.1X46-D40.2 Standard 18 Nov 2015
SRX5400 Junos 12.1X46-D40.2 (*1) Standard 18 Nov 2015
SRX5400 w/RE-1800X4 Junos 12.1X47-D20.7 Standard 11 May 2015
SRX5400 w/IOC3 Junos 15.1X49-D10.1 Standard 04 Sep 2015
SRX5600 Junos 12.1X46-D40.2 (*1) Standard 18 Nov 2015
SRX5600 w/RE-1800X4 Junos 12.1X47-D20.7 Standard 11 May 2015
SRX5600 w/IOC3 Junos 15.1X49-D10.1 Standard 04 Sep 2015
SRX5800 Junos 12.1X46-D40.2 (*1) Standard 18 Nov 2015
SRX5800 w/RE-1800X4 Junos 12.1X47-D20.7 Standard 11 May 2015
SRX5800 w/IOC3 Junos 15.1X49-D10.1 Standard 04 Sep 2015
Notes:
  1. KB29651 - Unable to upgrade from Junos OS 12.1X46 to subsequent releases of Junos OS on SRX5400/5600/5800 platforms due to "The /cf filesystem is low on free disk space" on SRX5k RE-13-20

Tuesday, 5 January 2016

ScreenOS 6.3.0r20 has been removed from the Juniper Support Download website

Product Affected:

SSG-5 (&Wireless,ADSL, ISDN, V92), SSG-20 (& Wireless), SSG-140, SSG300M-series, SSG 500/500M Series, ISG-1000, ISG-1000-IDP, ISG-2000, ISG-2000-IDP, NS-5000-MGT2/SPM2, NS-5000-MGT3/SPM3
 
Alert Description:

Reports of problems, after an upgrade, where SSH management, or msrpc traffic could cause the device to core dump.  Due to the severity of this issue, it is necessary to remove 6.3.0r20 from the software download website.
 
Solution:

The repaired version of ScreenOS is 6.3.0R21, and is now currently available.  

Wednesday, 23 December 2015

Out of Cycle Security Bulletin: ScreenOS: Multiple Security issues with ScreenOS

During an internal code review, two security issues were identified.

Administrative Access (CVE-2015-7755) allows unauthorized remote administrative access to the device. Exploitation of this vulnerability can lead to complete compromise of the affected device.

This issue only affects ScreenOS 6.3.0r17 through 6.3.0r20.  No other Juniper products or versions of ScreenOS are affected by this issue.

Upon exploitation of this vulnerability, the log file would contain an entry that ‘system’ had logged on followed by password authentication for a username.

Example:

Normal login by user username1:
2015-12-17 09:00:00 system warn 00515 Admin user username1 has logged on via SSH from …..
2015-12-17 09:00:00 system warn 00528 SSH: Password authentication successful for admin user ‘username1’ at host …


Compromised login by user username2:
2015-12-17 09:00:00 system warn 00515 Admin user system has logged on via SSH from …..
2015-12-17 09:00:00 system warn 00528 SSH: Password authentication successful for admin user ‘username2’ at host …


Note that a skilled attacker would likely remove these entries from the local log file, thus effectively eliminating any reliable signature that the device had been compromised.

This issue has been assigned CVE-2015-7755.


VPN Decryption (CVE-2015-7756) may allow a knowledgeable attacker who can monitor VPN traffic to decrypt that traffic. It is independent of the first issue.

This issue affects ScreenOS 6.2.0r15 through 6.2.0r18 and 6.3.0r12 through 6.3.0r20. No other Juniper products or versions of ScreenOS are affected by this issue.

There is no way to detect that this vulnerability was exploited.

This issue has been assigned CVE-2015-7756.


Juniper SIRT is not aware of any malicious exploitation of these vulnerabilities, however the password needed for the administrative access has been revealed publicly.

No other Juniper Networks products or platforms are affected by these issues.

Juniper has issued a statement about these vulnerabilities at: http://forums.juniper.net/t5/Security-Incident-Response/bg-p/SIRT
Solution:
The following software releases have been updated to resolve these specific issues: ScreenOS 6.2.0r19, 6.3.0r21, and all subsequent releases.

Additionally, earlier affected releases of ScreenOS 6.3.0 have been respun to resolve these issues. Fixes are included in: 6.3.0r12b, 6.3.0r13b, 6.3.0r14b, 6.3.0r15b, 6.3.0r16b, 6.3.0r17b, 6.3.0r18b, 6.3.0r19b.

All affected software releases on http://www.juniper.net/support/downloads/screenos.html have been updated with these fixes.

KB16765 - "In which releases are vulnerabilities fixed?" describes which release vulnerabilities are fixed as per our End of Engineering and End of Life support policies.
Workaround:
The Juniper SIRT strongly recommends upgrading to a fixed release (in Solution section above) to resolve these critical vulnerabilities.

CVE-2015-7755 (unauthorized access) Mitigation
Restricting management access to only trusted management networks and hosts will help mitigate this issue. The attack can only be executed from a location where a legitimate management login would be permitted.

CVE-2015-7756 (VPN decryption) Mitigation
No workaround or detection exists for the VPN decryption vulnerability.

Security Best Current Practice (BCP)
In addition to the recommendations listed above, it is good security practice to limit the exploitable attack surface of critical infrastructure networking equipment. Use access lists or firewall filters to limit management access to the device only from trusted, internal, administrative networks or hosts.

Implementation:
How to obtain fixed software:
ScreenOS software releases are available at http://www.juniper.net/support/downloads/screenos.html
loading...