Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2018-0056

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

Medium6.5EPSS 0.61%
Published
Updated
Reserved
Assigned by
juniper

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.

Scores

CVSS scores of CVE-2018-0056, by who scored it
Scored byCVSSScoreVector
juniperCNA (assigner)3.0Medium6.5CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.0Medium5.3CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.61% · top 51% of all CVEs (4 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.

Weakness

Affected products

  • Juniper Networks · Junos OS

    • affected 15.1 – < 15.1R7-S1
    • affected 16.1 – < 16.1R4-S12, 16.1R6-S6
    • affected 16.2 – < 16.2R2-S7
    • affected 17.1 – < 17.1R2-S9
    • affected 17.2 – < 17.2R1-S7, 17.2R2-S6
    • affected 17.3 – < 17.3R2-S4, 17.3R3-S1
    • affected 17.4 – < 17.4R1-S5
    • affected 18.1 – < 18.1R2

What to do

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.

Workaround: There are no viable workarounds for this issue

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

References (2)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2018-0056 badge
[![CVE-2018-0056](https://trackcve.app/badge/CVE-2018-0056.svg)](https://trackcve.app/cve/CVE-2018-0056)

Record last updated .