CVE-2019-0048

EX4300 Series: When a firewall filter is applied to a loopback interface, other firewall filters for multicast traffic may fail

State
Published
Severity
5.8 Medium
Published
Jul 11, 2019
Updated
Sep 17, 2024
Reserved
Oct 11, 2018

Read the record on cve.org

Description

On EX4300 Series switches with TCAM optimization enabled, incoming multicast traffic matches an implicit loopback filter rule first, since it has high priority. This rule is meant for reserved multicast addresses 224.0.0.x, but incorrectly matches on 224.x.x.x. Due to this bug, when a firewall filter is applied on the loopback interface, other firewall filters might stop working for multicast traffic. The command 'show firewall filter' can be used to confirm whether the filter is working. This issue only affects the EX4300 switch. No other products or platforms are affected by this vulnerability. This issue affects: Juniper Networks Junos OS: 14.1X53 versions prior to 14.1X53-D51, 14.1X53-D115 on EX4300 Series; 17.1 versions prior to 17.1R3 on EX4300 Series; 17.2 versions prior to 17.2R3-S2 on EX4300 Series; 17.3 versions prior to 17.3R3-S3 on EX4300 Series; 17.4 versions prior to 17.4R2-S5, 17.4R3 on EX4300 Series; 18.1 versions prior to 18.1R3-S1 on EX4300 Series; 18.2 versions prior to 18.2R2 on EX4300 Series; 18.3 versions prior to 18.3R2 on EX4300 Series.

Scores

CVSSScoreVectorSource
3.05.8 MediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:Njuniper

Weaknesses

Affected Products

ProductVersions
Junos OSJuniper Networks
  • 14.1X53 versions prior to 14.1X53-D51 and 14.1X53-D115 on EX4300 SeriesAffected
  • 17.1 versions prior to 17.1R3 on EX4300 SeriesAffected
  • 17.2 versions prior to 17.2R3-S2 on EX4300 SeriesAffected
  • 17.3 versions prior to 17.3R3-S3 on EX4300 SeriesAffected
  • 17.4 versions prior to 17.4R2-S5 and 17.4R3 on EX4300 SeriesAffected
  • 18.1 versions prior to 18.1R3-S1 on EX4300 SeriesAffected
  • 18.2 versions prior to 18.2R2 on EX4300 SeriesAffected
  • 18.3 versions prior to 18.3R2 on EX4300 SeriesAffected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.