CVE-2019-0057

HIGHNVD 7.87.8
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

An improper authorization weakness in Juniper Networks Junos OS allows a local authenticated attacker to bypass regular security controls to access the Junos Device Manager (JDM) application and take control of the system. This issue affects: Juniper Networks Junos OS versions prior to 18.2R1, 18.2X75-D5.

CVSS v3
7.8
EG Score
7.8(low)
EPSS
29.9%
KEV
Not listed

Published

October 9, 2019

Last Modified

November 21, 2024

References (2)

Data Freshness Timeline

(refreshed 12× in last 7d / 47× 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.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-07 13:42 UTCEPSS rescore
  3. 2026-07-06 16:25 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-05 02:27 UTCEPSS rescore
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-04 06:28 UTCEPSS rescore
  9. 2026-07-01 15:03 UTCEPSS rescore
  10. 2026-07-01 15:03 UTCEPSS rescore
  11. 2026-06-30 23:20 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-29 14:03 UTCEPSS rescore
  14. 2026-06-28 14:04 UTCEPSS rescore
  15. 2026-06-28 04:53 UTCEPSS rescore
  16. 2026-06-28 04:53 UTCEPSS rescore
  17. 2026-06-27 03:06 UTCEPSS rescore
  18. 2026-06-27 03:06 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-24 14:02 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-23 21:30 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-22 14:23 UTCEPSS rescore
Show 47 more
  1. 2026-06-22 14:23 UTCEPSS rescore
  2. 2026-06-21 14:54 UTCEPSS rescore
  3. 2026-06-21 14:54 UTCEPSS rescore
  4. 2026-06-21 01:57 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-19 19:23 UTCEPSS rescore
  7. 2026-06-19 19:23 UTCEPSS rescore
  8. 2026-06-18 17:50 UTCEPSS rescore
  9. 2026-06-18 17:50 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-16 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-06-14 23:15 UTCEPSS rescore
  15. 2026-06-14 23:15 UTCEPSS rescore
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-11 13:57 UTCEPSS rescore
  20. 2026-06-10 22:16 UTCEPSS rescore
  21. 2026-06-10 13:19 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-07 15:22 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
  26. 2026-06-06 13:45 UTCEPSS rescore
  27. 2026-06-05 22:45 UTCEPSS rescore
  28. 2026-06-05 22:45 UTCEPSS rescore
  29. 2026-06-05 06:08 UTCEPSS rescore
  30. 2026-06-05 06:08 UTCEPSS rescore
  31. 2026-06-04 13:10 UTCEPSS rescore
  32. 2026-06-04 13:10 UTCEPSS rescore
  33. 2026-06-01 13:50 UTCEPSS rescore
  34. 2026-05-31 22:29 UTCEPSS rescore
  35. 2026-05-31 22:29 UTCEPSS rescore
  36. 2026-05-31 00:14 UTCEPSS rescore
  37. 2026-05-31 00:14 UTCEPSS rescore
  38. 2026-05-29 13:41 UTCEPSS rescore
  39. 2026-05-28 13:43 UTCEPSS rescore
  40. 2026-05-28 13:42 UTCEPSS rescore
  41. 2026-05-27 13:38 UTCEPSS rescore
  42. 2026-05-26 13:42 UTCEPSS rescore
  43. 2026-05-26 13:42 UTCEPSS rescore
  44. 2026-05-26 07:17 UTCEPSS rescore
  45. 2026-05-26 07:17 UTCEPSS rescore
  46. 2026-05-23 03:16 UTCEG score recompute
  47. 2026-05-23 03:16 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2019-0057?
CVE-2019-0057 is a high vulnerability published on October 9, 2019. An improper authorization weakness in Juniper Networks Junos OS allows a local authenticated attacker to bypass regular security controls to access the Junos Device Manager (JDM) application and take control of the system. This issue affects: Juniper Networks Junos OS versions prior to 18.2R1,…
When was CVE-2019-0057 disclosed?
CVE-2019-0057 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-0057 actively exploited?
CVE-2019-0057 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-0057?
CVE-2019-0057 has a CVSS v3 base score of 7.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2019-0057?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0057, 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-0057

Explore →

Is Your Infrastructure Affected by CVE-2019-0057?

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