CVE-2023-22397

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 6.1 from GitHub Security Advisory published 2023-01-13. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.1Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Juniper Networks, Inc.) lists Juniper Networks Junos OS Evolved versions before 20.4R3-S4-EVO, 21.3 up to but not including 21.3R3-S1-EVO and 22.2 up to but not including 22.2R2-EVO as affected. No release containing a fix is confirmed on record.

An Allocation of Resources Without Limits or Throttling weakness in the memory management of the Packet Forwarding Engine (PFE) on Juniper Networks Junos OS Evolved PTX10003 Series devices allows an adjacently located attacker who has established certain preconditions and knowledge of the environment to send certain specific genuine packets to begin a Time-of-check Time-of-use (TOCTOU) Race Condition attack which will cause a memory leak to begin. Once this condition begins, and as long as the attacker is able to sustain the offending traffic, a Distributed Denial of Service (DDoS) event occurs. As a DDoS event, the offending packets sent by the attacker will continue to flow from one device to another as long as they are received and processed by any devices, ultimately causing a cascading outage to any vulnerable devices. Devices not vulnerable to the memory leak will process and forward the offending packet(s) to neighboring devices. Due to internal anti-flood security controls and mechanisms reaching their maximum limit of response in the worst-case scenario, all affected Junos OS Evolved devices will reboot in as little as 1.5 days. Reboots to restore services cannot be avoided once the memory leak begins. The device will self-recover after crashing and rebooting. Operator intervention isn't required to restart the device. This issue affects: Juniper Networks Junos OS Evolved on PTX10003: All versions prior to 20.4R3-S4-EVO; 21.3 versions prior to 21.3R3-S1-EVO; 21.4 versions prior to 21.4R2-S2-EVO, 21.4R3-EVO; 22.1 versions prior to 22.1R1-S2-EVO, 22.1R2-EVO; 22.2 versions prior to 22.2R2-EVO. To check memory, customers may VTY to the PFE first then execute the following show statement: show jexpr jtm ingress-main-memory chip 255 | no-more Alternatively one may execute from the RE CLI: request pfe execute target fpc0 command "show jexpr jtm ingress-main-memory chip 255 | no-more" Iteration 1: Example output: Mem type: NH, alloc type: JTM 136776 bytes used (max 138216 bytes used) 911568 bytes available (909312 bytes from free pages) Iteration 2: Example output: Mem type: NH, alloc type: JTM 137288 bytes used (max 138216 bytes used) 911056 bytes available (909312 bytes from free pages) The same can be seen in the CLI below, assuming the scale does not change: show npu memory info Example output: FPC0:NPU16 mem-util-jnh-nh-size 2097152 FPC0:NPU16 mem-util-jnh-nh-allocated 135272 FPC0:NPU16 mem-util-jnh-nh-utilization 6

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 13, 2023

Last Modified

November 21, 2024

References (1)

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 91 of 189 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 98 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-22397?
CVE-2023-22397 is a medium-severity vulnerability; its CVE record was published on January 13, 2023. An Allocation of Resources Without Limits or Throttling weakness in the memory management of the Packet Forwarding Engine (PFE) on Juniper Networks Junos OS Evolved PTX10003 Series devices allows an adjacently located attacker who has established certain preconditions and knowledge of the…
When was CVE-2023-22397 made public?
CVE-2023-22397 was made public on January 11, 2023: that is the date its CVE record's CNA, Juniper Networks, Inc., gives for when the vulnerability was made public. The CVE record itself was published on January 13, 2023. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-22397 actively exploited?
CVE-2023-22397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-22397?
CVE-2023-22397 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2023-22397?
No fix for CVE-2023-22397 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Juniper Networks, Inc.) lists Juniper Networks Junos OS Evolved versions before 20.4R3-S4-EVO, 21.3 up to but not including 21.3R3-S1-EVO and 22.2 up to but not including 22.2R2-EVO as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-22397

Explore →

Is Your Infrastructure Affected by CVE-2023-22397?

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

Book a Demo →Browse All CVEs