CVE-2017-2312

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 2%CVSS: 6.5Exploit: NoneExposed: 0

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

On Juniper Networks devices running Junos OS affected versions and with LDP enabled, a specific LDP packet destined to the RE (Routing Engine) will consume a small amount of the memory allocated for the rpd (routing protocol daemon) process. Over time, repeatedly receiving this type of LDP packet(s) will cause the memory to exhaust and the rpd process to crash and restart. It is not possible to free up the memory that has been consumed without restarting the rpd process. This issue affects Junos OS based devices with either IPv4 or IPv6 LDP enabled via the [protocols ldp] configuration (the native IPv6 support for LDP is available in Junos OS 16.1 and higher). The interface on which the packet arrives needs to have LDP enabled. The affected Junos versions are: 13.3 prior to 13.3R10; 14.1 prior to 14.1R8; 14.2 prior to 14.2R7-S6 or 14.2R8; 15.1 prior to 15.1F2-S14, 15.1F6-S4, 15.1F7, 15.1R4-S7, 15.1R5; 15.1X49 before 15.1X49-D70; 15.1X53 before 15.1X53-D230, 15.1X53-D63, 15.1X53-D70; 16.1 before 16.1R2. 16.2R1 and all subsequent releases have a resolution for this vulnerability.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
72.3%
KEV
Not listed

Published

April 24, 2017

Last Modified

May 13, 2026

References (6)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2017-2312?
CVE-2017-2312 is a medium vulnerability published on April 24, 2017. On Juniper Networks devices running Junos OS affected versions and with LDP enabled, a specific LDP packet destined to the RE (Routing Engine) will consume a small amount of the memory allocated for the rpd (routing protocol daemon) process. Over time, repeatedly receiving this type of LDP…
When was CVE-2017-2312 disclosed?
CVE-2017-2312 was first published in the National Vulnerability Database on April 24, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-2312 actively exploited?
CVE-2017-2312 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 72.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-2312?
CVE-2017-2312 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2017-2312?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-2312, 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-2017-2312

Explore →

Is Your Infrastructure Affected by CVE-2017-2312?

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

Start Free Scan →Browse All CVEs