CVE-2023-44195: Junos OS Evolved: Packets which are not destined to the router can reach the RE
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Juniper Networks Junos OS Evolved 21.3R3-S5-EVO, 21.4R3-S4-EVO, 22.1*-EVO.
Low priority for now. Upgrade to Juniper Networks Junos OS Evolved 21.3R3-S5-EVO, 21.4R3-S4-EVO, 22.1*-EVO or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An Improper Restriction of Communication Channel to Intended Endpoints vulnerability in the NetworkStack agent daemon (nsagentd) of Juniper Networks Junos OS Evolved allows an unauthenticated network based attacker to cause limited impact to the availability of the system. If specific packets reach the Routing-Engine (RE) these will be processed normally even if firewall filters are in place which should have prevented this. This can lead to a limited, increased consumption of resources resulting in a Denial-of-Service (DoS), and unauthorized access. CVE-2023-44196 is a prerequisite for this issue. This issue affects Juniper Networks Junos OS Evolved: * 21.3-EVO versions prior to 21.3R3-S5-EVO; * 21.4-EVO versions prior to 21.4R3-S4-EVO; * 22.1-EVO version 22.1R1-EVO and later; * 22.2-EVO version 22.2R1-EVO and later; * 22.3-EVO versions prior to 22.3R2-S2-EVO, 22.3R3-S1-EVO; * 22.4-EVO versions prior to 22.4R3-EVO. This issue doesn't not affected Junos OS Evolved versions prior to 21.3R1-EVO.
- Published
- Oct 12, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-923
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.3
- CNA · juniper
- 5.4
- 0.1 point gap
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| juniper | junos os evolved | cpe:2.3:o:juniper:junos_os_evolved |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (juniper). Independent of NVD's CPE analysis and usually ahead of it.
Juniper Networks Junos OS Evolved
- before 21.3R1-EVOnot affected · semver
- 21.3-EVO and later · before 21.3R3-S5-EVOaffected · semver
- 21.4-EVO and later · before 21.4R3-S4-EVOaffected · semver
- 22.1R1-EVO and later · before 22.1*-EVOaffected · semver
- 22.2R1-EVO and later · before 22.2*-EVOaffected · semver
- 22.3-EVO and later · before 22.3R2-S2-EVO, 22.3R3-S1-EVOaffected · semver
- 22.4-EVO and later · before 22.4R3-EVOaffected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junos os evolved21.4
- juniper junos os evolved22.1
- juniper junos os evolved22.2
- juniper junos os evolved22.3
- juniper junos os evolved22.4
- juniper junos os evolved23.1
- juniper junos os evolved23.2
Same product
juniper: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-21902Junos OS Evolved: PTX Series: A vulnerability allows a unauthenticated, network-based attacker to execute code as root43Plan
- CVE-2026-101990Junos OS and Junos OS Evolved: A BGP peer causes an rpd crash when flow-spec routes are re-advertised37Monitor
- CVE-2026-101986Junos OS and Junos OS Evolved: J-Web permits pre-authentication CGI execution37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-44189Oct 11, 2023 · Junos OS Evolved: PTX10003 Series: MAC address validation bypass vulnerability21Monitor
- ← EarlierCVE-2023-44190Oct 11, 2023 · Junos OS Evolved: PTX10001, PTX10004, PTX10008, PTX10016: MAC address validation bypass vulnerability21Monitor
- Later →CVE-2023-44196Oct 12, 2023 · Junos OS Evolved: PTX10003 Series: Packets which are not destined to the router can reach the RE26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Juniper Networks Junos OS Evolved | 21.3R3-S5-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 21.4R3-S4-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.1*-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.2*-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.3R2-S2-EVO, 22.3R3-S1-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.4R3-EVO | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-923 · Improper Restriction of Communication Channel to Intended EndpointsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.