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

2018-10 Security Bulletin: MX Series: L2ALD daemon may crash if a duplicate MAC is learned by two different interfaces (CVE-2018-0056)

0

0

Article ID: JSA10890 SECURITY_ADVISORIES Last Updated: 10 Oct 2018Version: 1.0
Product Affected:
This issue affects Junos OS 15.1, 16.1, 16.2, 17.1, 17.2, 17.3, 17.4, 18.1. Affected platforms: MX Series.
Problem:

If a duplicate MAC address is learned by two different interfaces on an MX Series device, the MAC address learning function correctly flaps between the interfaces. However, the Layer 2 Address Learning Daemon (L2ALD) daemon might crash when attempting to delete the duplicate MAC address when the particular entry is not found in the internal MAC address table.

This issue only occurs on MX Series devices with l2-backhaul VPN configured. No other products or platforms are affected by this issue.

Affected releases are Juniper Networks Junos OS:

  • 15.1 versions prior to 15.1R7-S1 on MX Series;
  • 16.1 versions prior to 16.1R4-S12, 16.1R6-S6 on MX Series;
  • 16.2 versions prior to 16.2R2-S7 on MX Series;
  • 17.1 versions prior to 17.1R2-S9 on MX Series;
  • 17.2 versions prior to 17.2R1-S7, 17.2R2-S6 on MX Series;
  • 17.3 versions prior to 17.3R2-S4, 17.3R3-S1 on MX Series;
  • 17.4 versions prior to 17.4R1-S5 on MX Series;
  • 18.1 versions prior to 18.1R2 on MX Series.

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-2018-0056.
 

Solution:

The following software releases have been updated to resolve this specific issue: 15.1R7-S1, 16.1R4-S12, 16.1R6-S6, 16.1R7, 16.2R2-S7, 16.2R3, 17.1R2-S9, 17.1R3, 17.2R1-S7, 17.2R2-S6, 17.2R3, 17.3R2-S4, 17.3R3-S1, 17.4R1-S5, 17.4R2, 18.1R2, 18.2R1, and all subsequent releases.

This fix has also been proactively committed into Junos OS: 15.1X49-D150, 15.1X53-D235, 15.1X53-D495, 15.1X53-D590, 15.1X53-D68, 18.2X75-D5, and all subsequent releases.

This issue is being tracked as PR 1338688 which is visible on the Customer Support website.

Note: Juniper SIRT's policy is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).
 

Workaround:
There are no viable workarounds for this issue.
 
Implementation:
Software Releases, patches and updates are available at https://www.juniper.net/support/downloads/.
 
Modification History:
‚Äč2018-10-10: Initial publication

CVSS Score:
6.5 (CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Severity Level:
Medium
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