2016-07 Security Bulletin: SRX Series: On High-End SRX-Series, ALG’s applied to in-transit traffic may trigger high CP (central point) utilization leading to denial of services. (CVE-2016-1276)Product Affected:This issue affects both standalone or cluster mode configurations with different denial of service permutations on High-End SRX-Series chassis.
Problem:When High-End SRX-Series chassis have policies with one or more ALG’s (application layer gateways) enabled, which are applied to in-transit traffic, this may trigger a number of failure conditions which could cause various types of denials of service to traffic in-transit.Continued in-transit traffic matching ALG rules can create a sustained denial of service.This issue affects both standalone or cluster mode configurations with different denial of service permutations.Standalone:
In standalone HE chassis deployments, existing sessions will function normally, new session establishment due to high CP utilization may cause new sessions to not establish.

Cluster: 
In cluster HE chassis deployments, the fab link between chassis may be unable to sustain communication causing the backup to go ineligible due to fab link failure.
New sessions setups due to high CP utilization may be unable to be established.
The primary chassis processing LACP communication may lose LACP links triggering failover conditions which could create sustained flip-flop failovers between each chassis, including possible line card reboots, leading to long term denials of service.

This issue only affects devices when one, some, many and/or all ALG’s are enabled and traffic conditions match triggering any ALG.  See KB25546 for the ALG list.Juniper SIRT is not aware of any malicious exploitation of this vulnerability.No other Juniper Networks products or platforms are affected by this issue.This issue has been assigned CVE-2016-1276.
Solution:The following software releases have been updated to resolve this specific issue: Junos OS 12.1X46-D50, 12.1X47-D23, 12.1X47-D35, 12.3X48-D25, 15.1X49-D40 and subsequent releases.This issue is being tracked as PR 1150971 and is visible on the Customer Support website.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 following workarounds may be used to mitigate, reduce or resolve the risk of the problem from occuring:
Disabling all ALG’s will mitigate the issue until such time that an upgrade can be performed on the chassis.
Breaking cluster nodes if present and operating standalone High End SRX-Series Service Gateways in parallel while also distributing traffic equally between both standalone devices may reduce the number of high CP utilization on each chassis and may mitigate the risk of line card reboots.

Implementation: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.Modification History:
2016-07-13: Initial publication2016-07-22: Added language that any and all ALG’s are impacted by this JSA.

Related Links:CVSS Score:7.5 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Risk Level:High
Risk Assessment:Information for how Juniper Networks uses CVSS can be found at KB 16446 “Common Vulnerability Scoring System (CVSS) and Juniper’s Security Advisories.”
Acknowledgements:

Leave a Reply