CVE-2018-0056

MX Series: L2ALD daemon may crash if a duplicate MAC is learned by two different interfaces

MEDIUM

6.5

CVSS Score

Published: October 10, 2018 at 06:00 PM UTC

Updated: June 17, 2026 at 01:29 AM UTC

1 product affected across 1 vendorJunos

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM6.5

Exploit prediction

EPSS 0.6%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Junos · Juniper Networks

95%

15.1 ≤ v < 15.1R7-S116.1 ≤ v < 16.1R4-S12, 16.1R6-S616.2 ≤ v < 16.2R2-S717.1 ≤ v < 17.1R2-S917.2 ≤ v < 17.2R1-S7, 17.2R2-S617.3 ≤ v < 17.3R2-S4, 17.3R3-S117.4 ≤ v < 17.4R1-S518.1 ≤ v < 18.1R215.1 15.1 f2 15.1 f3 15.1 f4 15.1 f5 15.1 f6 15.1 r1 15.1 r2 15.1 r3 15.1 r4 15.1 r5 15.1 r6 16.1 16.1 r1 16.1 r2 16.1 r3 16.2 16.2 r1 17.1 17.1 r1 17.2 17.3 17.3 r1 17.4 17.4 r1 18.1 18.1 r1

Affected range stops below 15.1R7-S1, so it looks safe — our inference, not a vendor statement

Affected range stops below 16.1R4-S12, 16.1R6-S6, so it looks safe — our inference, not a vendor statement

Affected range stops below 16.2R2-S7, so it looks safe — our inference, not a vendor statement

Affected range stops below 17.1R2-S9, so it looks safe — our inference, not a vendor statement

Affected range stops below 17.2R1-S7, 17.2R2-S6, so it looks safe — our inference, not a vendor statement

Affected range stops below 17.3R2-S4, 17.3R3-S1, so it looks safe — our inference, not a vendor statement

Affected range stops below 17.4R1-S5, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.1R2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://kb.juniper.net/JSA10890

References (2)

VDB Entryx_refsource_SECTRACKThird Party Advisory

Source: [email protected]

http://www.securitytracker.com/id/1041857

x_refsource_CONFIRMVendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA10890

CVSS

6.5MEDIUMjuniper

Attack Vector: ADJACENT_NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: HIGH

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card