Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

2020-01 Security Bulletin: Junos OS: Improper handling of specific IPv6 packets sent by clients eventually kernel crash (vmcore) the device. (CVE-2020-1603)

0

1

Article ID: JSA10982 SECURITY_ADVISORIES Last Updated: 10 Jan 2020Version: 7.0
Product Affected:
This issue affects Junos OS 16.1, 16.2, 17.1, 17.2, 17.3, 17.4, 18.1, 18.2, 18.2X75, 18.3, 18.4, 19.1, 19.2.
Problem:

Specific IPv6 packets sent by clients processed by the Routing Engine (RE) are improperly handled. These IPv6 packets are designed to be blocked by the RE from egressing the RE. Instead, the RE allows these specific IPv6 packets to egress the RE, at which point a mbuf memory leak occurs within the Juniper Networks Junos OS device. This memory leak eventually leads to a kernel crash (vmcore), or the device hanging and requiring a power cycle to restore service, creating a Denial of Service (DoS) condition.

During the time where mbufs are rising, yet not fully filled, some traffic from client devices may begin to be black holed. To be black holed, this traffic must match the condition where this traffic must be processed by the RE.

Continued receipt and attempted egress of these specific IPv6 packets from the Routing Engine (RE) will create an extended Denial of Service (DoS) condition.

Scenarios which have been observed are:

1. In a single chassis, single RE scenario, the device will hang without vmcore, or a vmcore may occur and then hang. In this scenario the device needs to be power cycled.

2. In a single chassis, dual RE scenario, the device master RE will fail over to the backup RE. In this scenario, the master and the backup REs need to be reset from time to time when they vmcore. There is no need to power cycle the device.

3. In a dual chassis, single RE scenario, the device will hang without vmcore, or a vmcore may occur and then hang. In this scenario, the two chassis' design relies upon some type of network level redundancy - VRRP, GRES, NSR, etc. -

3.a In a commanded switchover, where nonstop active routing (NSR) is enabled no session loss is observed.

4. In a dual chassis, dual chassis scenario, rely upon the RE to RE failover as stated in the second scenario. In the unlikely event that the device does not switch RE to RE gracefully, then the fallback position is to the network level services scenario in the third scenario.

This issue affects:

Juniper Networks Junos OS

16.1 versions prior to 16.1R7-S6;

16.1 version 16.1X70-D10 and later;

16.2 versions prior to 16.2R2-S11;

17.1 versions prior to 17.1R2-S11, 17.1R3-S1;

17.2 versions prior to 17.2R1-S9, 17.2R2-S8, 17.2R3-S3;

17.3 versions prior to 17.3R3-S6;

17.4 versions prior to 17.4R2-S9, 17.4R3;

18.1 versions prior to 18.1R3-S7;

18.2 versions prior to 18.2R3-S2;

18.2X75 versions prior to 18.2X75-D50, 18.2X75-D410;

18.3 versions prior to 18.3R1-S6, 18.3R2-S2, 18.3R3;

18.4 versions prior to 18.4R2-S2, 18.4R3;

19.1 versions prior to 19.1R1-S3, 19.1R2;

19.2 versions prior to 19.2R1-S2, 19.2R2.

This issue does not affect releases prior to Junos OS 16.1R1.

This issue may occur when an interface is configured with IPv6.

For example:

[interfaces fe-1/2/0 unit 1 family inet6 address 2001:db8:0:1::/64]

Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

This issue was seen during production usage.

This issue has been assigned CVE-2020-1603.

Solution:

The following software releases have been updated to resolve this specific issue: 16.1R7-S6, 16.2R2-S11, 17.1R2-S11, 17.1R3-S1, 17.2R1-S9, 17.2R2-S8, 17.2R3-S3, 17.3R3-S6, 17.4R2-S5, 17.3R2-S6, 17.4R3, 18.1R3-S7, 18.2R3-S2, 18.2X75-D50, 18.2X75-D410, 18.3R1-S6, 18.3R2-S2, 18.3R3, 18.4R2-S2, 18.4R3, 19.1R1-S3, 19.1R2, 19.2R1-S2, 19.2R2, 19.3R1, and all subsequent releases.

This issue is being tracked as 1443576.

Workaround:

Remove 'family inet6' from interfaces. Otherwise, there are no available workarounds for this issue.

Indicators of compromise can be found by reviewing RE logs for entries which match in " " :
"/kernel: Mbuf: High Utililization Level"

Additionally, you may issue the follow command from time to time to determine if your mbufs are climbing or are being released by reviewing across two separate times.

The required privilege level to run the command is: view.

show system buffers


 
Implementation:
Software Releases, patches and updates are available at https://www.juniper.net/support/downloads/.    
Modification History:
2020-01-08: Initial Publication.
2020-01-10: Updated title, description and workaround section to clarify scenarios and minimize the language of "black hole" traffic.
CVSS Score:
8.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H)
Severity Level:
High
Severity Assessment:
Information for how Juniper Networks uses CVSS can be found at KB 16446 "Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories."

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search