CVE-2019-0063

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 1.3%, top 33% of all CVEs by exploit prediction. 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

When an MX Series Broadband Remote Access Server (BRAS) is configured as a Broadband Network Gateway (BNG) with DHCPv6 enabled, jdhcpd might crash when receiving a specific crafted DHCP response message on a subscriber interface. The daemon automatically restarts without intervention, but continuous receipt of specific crafted DHCP messages will repeatedly crash jdhcpd, leading to an extended Denial of Service (DoS) condition. This issue only affects systems configured with DHCPv6 enabled. DHCPv4 is unaffected by this issue. This issue affects Juniper Networks Junos OS: 15.1 versions prior to 15.1R7-S5 on MX Series; 16.1 versions prior to 16.1R7-S5 on MX Series; 16.2 versions prior to 16.2R2-S10 on MX Series; 17.1 versions prior to 17.1R3-S1 on MX Series; 17.2 versions prior to 17.2R3-S2 on MX Series; 17.3 versions prior to 17.3R3-S6 on MX Series; 17.4 versions prior to 17.4R2-S5, 17.4R3 on MX Series; 18.1 versions prior to 18.1R3-S6 on MX Series; 18.2 versions prior to 18.2R2-S4, 18.2R3 on MX Series; 18.2X75 versions prior to 18.2X75-D50 on MX Series; 18.3 versions prior to 18.3R1-S5, 18.3R3 on MX Series; 18.4 versions prior to 18.4R2 on MX Series; 19.1 versions prior to 19.1R1-S2, 19.1R2 on MX Series.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

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
Severity65% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
68%
KEV
Not listed

Published

October 9, 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 / 30× 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 122 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-0063?
CVE-2019-0063 is a medium vulnerability published on October 9, 2019. When an MX Series Broadband Remote Access Server (BRAS) is configured as a Broadband Network Gateway (BNG) with DHCPv6 enabled, jdhcpd might crash when receiving a specific crafted DHCP response message on a subscriber interface. The daemon automatically restarts without intervention, but…
When was CVE-2019-0063 disclosed?
CVE-2019-0063 was first published in the National Vulnerability Database on October 9, 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-0063 actively exploited?
CVE-2019-0063 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 32.2% of all scored CVEs.
What is the CVSS score of CVE-2019-0063?
CVE-2019-0063 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2019-0063?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0063, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2019-0063?

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

Start Free Scan →Browse All CVEs