CVE-2023-22396

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2023-01-13. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

The following software releases have been updated to resolve this specific issue: 19.3R3-S7, 19.4R3-S10, 20.2R3-S6, 20.3R3-S6, 20.4R3-S5, 21.1R3-S4, 21.2R3-S3, 21.3R3-S2, 21.4R3, 22.1R2-S1, 22.1R3, 22.2R1-S2, 22.2R2, 22… (from the CVE record's solution, Juniper Networks, Inc.) — apply it.

An Uncontrolled Resource Consumption vulnerability in TCP processing on the Routing Engine (RE) of Juniper Networks Junos OS allows an unauthenticated network-based attacker to send crafted TCP packets destined to the device, resulting in an MBUF leak that ultimately leads to a Denial of Service (DoS). The system does not recover automatically and must be manually restarted to restore service. This issue occurs when crafted TCP packets are sent directly to a configured IPv4 or IPv6 interface on the device. Transit traffic will not trigger this issue. MBUF usage can be monitored through the use of the 'show system buffers' command. For example: user@junos> show system buffers | refresh 5 4054/566/4620 mbufs in use (current/cache/total) ... 4089/531/4620 mbufs in use (current/cache/total) ... 4151/589/4740 mbufs in use (current/cache/total) ... 4213/527/4740 mbufs in use (current/cache/total) This issue affects Juniper Networks Junos OS: 12.3 version 12.3R12-S19 and later versions; 15.1 version 15.1R7-S10 and later versions; 17.3 version 17.3R3-S12 and later versions; 18.4 version 18.4R3-S9 and later versions; 19.1 version 19.1R3-S7 and later versions; 19.2 version 19.2R3-S3 and later versions; 19.3 version 19.3R2-S7, 19.3R3-S3 and later versions prior to 19.3R3-S7; 19.4 version 19.4R2-S7, 19.4R3-S5 and later versions prior to 19.4R3-S10; 20.1 version 20.1R3-S1 and later versions; 20.2 version 20.2R3-S2 and later versions prior to 20.2R3-S6; 20.3 version 20.3R3-S1 and later versions prior to 20.3R3-S6; 20.4 version 20.4R2-S2, 20.4R3 and later versions prior to 20.4R3-S5; 21.1 version 21.1R2 and later versions prior to 21.1R3-S4; 21.2 version 21.2R1-S1, 21.2R2 and later versions prior to 21.2R3-S3; 21.3 versions prior to 21.3R3-S2; 21.4 versions prior to 21.4R3; 22.1 versions prior to 22.1R2-S1, 22.1R3; 22.2 versions prior to 22.2R1-S2, 22.2R2; 22.3 versions prior to 22.3R1-S1, 22.3R2.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 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: The following software releases have been updated to resolve this specific issue: 19.3R3-S7, 19.4R3-S10, 20.2R3-S6, 20.3R3-S6, 20.4R3-S5, 21.1R3-S4, 21.2R3-S3, 21.3R3-S2, 21.4R3, 22.1R2-S1, 22.1R3, 22.2R1-S2, 22.2R2, 22… (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
46th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% 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.

The following software releases have been updated to resolve this specific issue: 19.3R3-S7, 19.4R3-S10, 20.2R3-S6, 20.3R3-S6, 20.4R3-S5, 21.1R3-S4, 21.2R3-S3, 21.3R3-S2, 21.4R3, 22.1R2-S1, 22.1R3, 22.2R1-S2, 22.2R2, 22… (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines.

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(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 34× 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 93 of 191 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. 7 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.6% · 46th percentile
  2. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-10-21 04:59 UTCEG score recompute
  5. 2026-10-21 04:59 UTCGHSA enrichmentGHSA-6c7f-v79h-5rvh · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  7. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  8. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  9. 2026-10-18 08:13 UTCEG score recompute
  10. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-12 18:36 UTCEG score recompute
  16. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-11 21:59 UTCEG score recompute
  18. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  25. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.6% · 44th percentile
Show 68 more
  1. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  2. 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  3. 2026-10-01 19:47 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  4. 2026-09-30 16:17 UTCEG score recompute
  5. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  6. 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  7. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  8. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  9. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  10. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-09-22 14:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-09-17 19:24 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  22. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  23. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  25. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  26. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  27. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  28. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  29. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  30. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  31. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  32. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  33. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  34. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  35. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  36. 2026-08-24 14:14 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  37. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  38. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  39. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  40. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  41. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  42. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  43. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  44. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  45. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  46. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  47. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  48. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  49. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  50. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  51. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  52. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  53. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  54. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  55. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  56. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  57. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  58. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  59. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  60. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  61. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  62. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  63. 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  64. 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  65. 2026-07-23 02:18 UTCEG score recompute
  66. 2026-07-22 23:06 UTCEG score recompute
  67. 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  68. 2026-07-21 15:23 UTCEPSS rescoreEPSS 0.6% · 43rd percentile

Frequently asked(5)

What is CVE-2023-22396?
CVE-2023-22396 is a high-severity vulnerability; its CVE record was published on January 13, 2023. An Uncontrolled Resource Consumption vulnerability in TCP processing on the Routing Engine (RE) of Juniper Networks Junos OS allows an unauthenticated network-based attacker to send crafted TCP packets destined to the device, resulting in an MBUF leak that ultimately leads to a Denial of Service…
When was CVE-2023-22396 made public?
CVE-2023-22396 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-22396 actively exploited?
CVE-2023-22396 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-22396?
CVE-2023-22396 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-22396?
The CVE record's solution for CVE-2023-22396, written by its CNA Juniper Networks, Inc., names the fix: "The following software releases have been updated to resolve this specific issue: 19.3R3-S7, 19.4R3-S10, 20.2R3-S6, 20.3R3-S6, 20.4R3-S5, 21.1R3-S4, 21.2R3-S3, 21.3R3-S2, 21.4R3, 22.1R2-S1, 22.1R3, 22.2R1-S2, 22.2R2, 22…"

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2023-22396?

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