CVE-2019-0048
Last modified
CVE-2019-0048 is a medium-severity vulnerability rated 5.8/10 on the CVSS scale. 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. EPSS estimates a 0.97% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Juniper | Junos | 14.1x53 |
| Juniper | Junos | 17.1 |
| Juniper | Junos | 17.2 |
| Juniper | Junos | 17.3 |
| Juniper | Junos | 17.4 |
| Juniper | Junos | 18.1 |
| Juniper | Junos | 18.2 |
| Juniper | Junos | 18.3 |
References
- https://kb.juniper.net/JSA10942Patch, Vendor Advisory
- https://kb.juniper.net/JSA10942Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-0048?
How severe is CVE-2019-0048?
How do I fix CVE-2019-0048?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2019
- CVE-2019-0041On EX4300-MP Series devices with any lo0 filters applied, tr…8.6
- CVE-2019-0042Juniper Identity Management Service (JIMS) for Windows versi…4.2
- CVE-2019-0043In MPLS environments, receipt of a specific SNMP packet may …7.5
- CVE-2019-0044Receipt of a specific packet on the out-of-band management i…7.5
- CVE-2019-0046A vulnerability in the pfe-chassisd Chassis Manager (CMLC) d…6.5
- CVE-2019-0047A persistent Cross-Site Scripting (XSS) vulnerability in Jun…8.8
- CVE-2019-0049On Junos devices with the BGP graceful restart helper mode e…7.5
- CVE-2019-0050Under certain heavy traffic conditions srxpfe process can cr…7.5
- CVE-2019-0051SSL-Proxy feature on SRX devices fails to handle a hardware …7.5
- CVE-2019-0052The srxpfe process may crash on SRX Series services gateways…7.5
- CVE-2019-0053Insufficient validation of environment variables in the teln…7.8
- CVE-2019-0054An Improper Certificate Validation weakness in the SRX Serie…7.4
Are you affected by CVE-2019-0048?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
