An Improper Handling of Unexpected Data Type vulnerability in IPv6 firewall filter processing of Juniper Networks Junos OS on the ACX Series devices will prevent a firewall filter with the term 'from next-header ah' from being properly installed in the packet forwarding engine (PFE). There is no immediate indication of an incomplete firewall filter commit shown at the CLI, which could allow an attacker to send valid packets to or through the device that were explicitly intended to be dropped. An indication that the filter was not installed can be identified with the following logs: fpc0 ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_rule_prepare : Config failed: Unsupported Ip-protocol 51 in the filter lo0.0-inet6-i fpc0 ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_rule_prepare : Please detach the filter, remove unsupported match and re-attach fpc0 ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_process_rule : Status:104 dnx_dfw_rule_prepare failed fpc0 ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_process_filter : Status:104 dnx_dfw_process_rule failed fpc0 ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_update_filter_in_hw : Status:104 Could not process filter(lo0.0-inet6-i) for rule expansion Unsupported match, action present. fpc0 ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_create_hw_instance : Status:104 Could not program dfw(lo0.0-inet6-i) type(IFP_DFLT_INET6_Lo0_FILTER)! [104] fpc0 ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_bind_shim : [104] Could not create dfw(lo0.0-inet6-i) type(IFP_DFLT_INET6_Lo0_FILTER) fpc0 ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_update_resolve : [100] Failed to bind filter(3) to bind point fpc0 ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_change_end : dnx_dfw_update_resolve (resolve type) failed This issue affects Juniper Networks Junos OS on ACX Series: All versions prior to 20.2R3-S7; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S3; 21.2 versions prior to 21.2R3-S4; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R3; 22.1 versions prior to 22.1R2.
CVE-2023-28961
“—” beside the score: it is equal to NVD's CVSS score.
Score 5.8 from GitHub Security Advisory published 2023-04-18. NVD baseline CVSS 5.8; sources differ by 0.0.
- Lower severity and no public exploit yet
The following software releases have been updated to resolve this specific issue: 20.2R3-S7, 20.4R3-S4, 21.1R3-S3, 21.2R3-S4, 21.3R3, 21.4R3, 22.1R2, 22.2R1, and all subsequent releases (from the CVE record's solution, Juniper Networks, Inc.) — apply it.
- CVSS v3
- 5.8
- EG Score
- 5.8MEDIUMmedium confidence
- EG Risk
- 41EG Risk 41/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)Severity58% × 45%Impact severity (EG Severity): CVSS 5.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (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: 20.2R3-S7, 20.4R3-S4, 21.1R3-S3, 21.2R3-S4, 21.3R3, 21.4R3, 22.1R2, 22.2R1, and all subsequent releases (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 35th
- 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 (5.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).
The following software releases have been updated to resolve this specific issue: 20.2R3-S7, 20.4R3-S4, 21.1R3-S3, 21.2R3-S4, 21.3R3, 21.4R3, 22.1R2, 22.2R1, and all subsequent releases (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (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
April 17, 2023
Last Modified
November 21, 2024
References (1)
- sirt@juniper · CVE Programhttps://supportportal.juniper.net/JSA70586Vendor Advisory
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 33× 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 186 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 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 08:06 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-12 18:29 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-11 21:55 UTCEG score recompute
- 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 66 moreShow fewer
- 2026-10-01 19:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-30 16:21 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-22 14:45 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-24 14:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-27 14:10 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-23 02:21 UTCEG score recompute
- 2026-07-22 23:09 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-21 15:23 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-07-20 17:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2023-28961?
When was CVE-2023-28961 made public?
Is CVE-2023-28961 actively exploited?
What is the CVSS score of CVE-2023-28961?
How do I remediate CVE-2023-28961?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-28961
Is Your Infrastructure Affected by CVE-2023-28961?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.