CVE-2019-0048

MEDIUMNVD 5.85.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.8 under NVD CVSS v3. EPSS exploit probability: 1.0% (60th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 5.8Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.

CVSS v3
5.8
EG Score
5.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity58% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
1.0%
EPSS %ILE
60th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 11, 2019

Last Modified

November 21, 2024

References (2)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 156 total refreshes for this CVE.

  1. 2026-10-05 17:39 UTCEPSS rescore
  2. 2026-10-04 23:18 UTCEPSS rescore
  3. 2026-10-03 14:21 UTCEPSS rescore
  4. 2026-10-01 19:44 UTCEPSS rescore
  5. 2026-09-30 14:59 UTCEPSS rescore
  6. 2026-09-30 10:06 UTCEG score recompute
  7. 2026-09-29 15:12 UTCEPSS rescore
  8. 2026-09-28 13:46 UTCEPSS rescore
  9. 2026-09-27 13:40 UTCEPSS rescore
  10. 2026-09-26 15:53 UTCEPSS rescore
  11. 2026-09-24 13:59 UTCEPSS rescore
  12. 2026-09-23 13:42 UTCEPSS rescore
  13. 2026-09-21 20:27 UTCEPSS rescore
  14. 2026-09-20 20:10 UTCEPSS rescore
  15. 2026-09-19 15:36 UTCEPSS rescore
  16. 2026-09-18 19:22 UTCEPSS rescore
  17. 2026-09-17 19:22 UTCEPSS rescore
  18. 2026-09-15 03:05 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-13 16:42 UTCEPSS rescore
  21. 2026-09-11 14:48 UTCEPSS rescore
  22. 2026-09-11 09:32 UTCEPSS rescore
  23. 2026-09-06 13:44 UTCEPSS rescore
  24. 2026-09-04 13:56 UTCEPSS rescore
  25. 2026-09-04 05:02 UTCEPSS rescore
Show 75 more
  1. 2026-09-02 14:07 UTCEPSS rescore
  2. 2026-09-01 03:32 UTCEPSS rescore
  3. 2026-08-30 19:13 UTCEPSS rescore
  4. 2026-08-30 01:18 UTCEPSS rescore
  5. 2026-08-28 21:36 UTCEPSS rescore
  6. 2026-08-27 14:21 UTCEPSS rescore
  7. 2026-08-26 14:42 UTCEPSS rescore
  8. 2026-08-25 13:45 UTCEPSS rescore
  9. 2026-08-24 14:11 UTCEPSS rescore
  10. 2026-08-21 23:45 UTCEPSS rescore
  11. 2026-08-20 22:51 UTCEPSS rescore
  12. 2026-08-19 17:00 UTCEPSS rescore
  13. 2026-08-18 13:44 UTCEPSS rescore
  14. 2026-08-17 13:43 UTCEPSS rescore
  15. 2026-08-16 14:52 UTCEPSS rescore
  16. 2026-08-16 02:10 UTCEPSS rescore
  17. 2026-08-15 01:26 UTCEPSS rescore
  18. 2026-08-13 21:56 UTCEPSS rescore
  19. 2026-08-12 13:47 UTCEPSS rescore
  20. 2026-08-09 13:43 UTCEPSS rescore
  21. 2026-08-08 16:32 UTCEPSS rescore
  22. 2026-08-07 16:23 UTCEPSS rescore
  23. 2026-08-06 13:42 UTCEPSS rescore
  24. 2026-08-04 15:05 UTCEPSS rescore
  25. 2026-08-04 10:33 UTCEPSS rescore
  26. 2026-08-03 10:31 UTCEPSS rescore
  27. 2026-08-02 02:23 UTCEPSS rescore
  28. 2026-08-01 04:12 UTCEPSS rescore
  29. 2026-07-30 16:24 UTCEPSS rescore
  30. 2026-07-30 01:27 UTCEPSS rescore
  31. 2026-07-28 15:32 UTCEPSS rescore
  32. 2026-07-27 14:05 UTCEPSS rescore
  33. 2026-07-26 14:51 UTCEPSS rescore
  34. 2026-07-25 14:14 UTCEPSS rescore
  35. 2026-07-25 14:14 UTCEPSS rescore
  36. 2026-07-24 14:14 UTCEPSS rescore
  37. 2026-07-24 14:14 UTCEPSS rescore
  38. 2026-07-23 14:15 UTCEPSS rescore
  39. 2026-07-23 14:15 UTCEPSS rescore
  40. 2026-07-23 01:38 UTCEG score recompute
  41. 2026-07-22 22:18 UTCEG score recompute
  42. 2026-07-22 14:05 UTCEPSS rescore
  43. 2026-07-21 15:22 UTCEPSS rescore
  44. 2026-07-20 17:04 UTCEPSS rescore
  45. 2026-07-20 17:04 UTCEPSS rescore
  46. 2026-07-19 14:28 UTCEPSS rescore
  47. 2026-07-19 14:28 UTCEPSS rescore
  48. 2026-07-19 02:26 UTCEPSS rescore
  49. 2026-07-19 02:26 UTCEPSS rescore
  50. 2026-07-16 16:59 UTCEPSS rescore
  51. 2026-07-16 16:59 UTCEPSS rescore
  52. 2026-07-15 16:55 UTCEPSS rescore
  53. 2026-07-15 01:56 UTCEPSS rescore
  54. 2026-07-13 22:27 UTCEPSS rescore
  55. 2026-07-13 06:10 UTCEPSS rescore
  56. 2026-07-12 05:43 UTCEPSS rescore
  57. 2026-07-09 19:06 UTCEPSS rescore
  58. 2026-07-08 15:11 UTCEPSS rescore
  59. 2026-07-08 15:11 UTCEPSS rescore
  60. 2026-07-07 13:42 UTCEPSS rescore
  61. 2026-07-07 13:42 UTCEPSS rescore
  62. 2026-07-06 16:25 UTCEPSS rescore
  63. 2026-07-06 16:24 UTCEPSS rescore
  64. 2026-07-06 02:20 UTCEPSS rescore
  65. 2026-07-05 02:27 UTCEPSS rescore
  66. 2026-07-04 06:28 UTCEPSS rescore
  67. 2026-07-04 06:28 UTCEPSS rescore
  68. 2026-07-01 15:03 UTCEPSS rescore
  69. 2026-07-01 15:03 UTCEPSS rescore
  70. 2026-06-30 23:20 UTCEPSS rescore
  71. 2026-06-30 23:20 UTCEPSS rescore
  72. 2026-06-28 14:04 UTCEPSS rescore
  73. 2026-06-28 04:53 UTCEPSS rescore
  74. 2026-06-28 04:53 UTCEPSS rescore
  75. 2026-06-27 03:06 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-0048?
CVE-2019-0048 is a medium vulnerability published on July 11, 2019. 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…
When was CVE-2019-0048 disclosed?
CVE-2019-0048 was first published on July 11, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0048 actively exploited?
CVE-2019-0048 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-0048?
CVE-2019-0048 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2019-0048?
A fix for CVE-2019-0048 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-0048

Explore →

Is Your Infrastructure Affected by CVE-2019-0048?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs