CVE-2023-44196: Junos OS Evolved: PTX10003 Series: Packets which are not destined to the router can reach the RE
Noroxi assessment
Priority: Monitor (action score 26/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.27% (FIRST EPSS).
- Someone on the same network segment 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 20.4R3-S8-EVO, 21.1*-EVO, 21.2R3-S6-EVO.
Low priority for now. Upgrade to Juniper Networks Junos OS Evolved 20.4R3-S8-EVO, 21.1*-EVO, 21.2R3-S6-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 Check for Unusual or Exceptional Conditions in the Packet Forwarding Engine (pfe) of Juniper Networks Junos OS Evolved on PTX10003 Series allows an unauthenticated adjacent attacker to cause an impact to the integrity of the system. When specific transit MPLS packets are received by the PFE, these packets are internally forwarded to the RE. This issue is a prerequisite for CVE-2023-44195. This issue affects Juniper Networks Junos OS Evolved: * All versions prior to 20.4R3-S8-EVO; * 21.1-EVO version 21.1R1-EVO and later; * 21.2-EVO versions prior to 21.2R3-S6-EVO; * 21.3-EVO version 21.3R1-EVO and later; * 21.4-EVO versions prior to 21.4R3-S3-EVO; * 22.1-EVO versions prior to 22.1R3-S4-EVO; * 22.2-EVO versions prior to 22.2R3-S3-EVO; * 22.3-EVO versions prior to 22.3R2-S2-EVO, 22.3R3-EVO; * 22.4-EVO versions prior to 22.4R2-EVO.
- Published
- Oct 12, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- CWE-754
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · juniper
- 6.5
- agree
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
| juniper | ptx10003 | cpe:2.3:h:juniper:ptx10003 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junos os evolvedbefore 20.4
- juniper junos os evolved20.4
- juniper junos os evolved21.1
- juniper junos os evolved21.2
- juniper junos os evolved21.3
- 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
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 20.4R3-S8-EVOaffected · semver
- 21.1R1-EVO and later · before 21.1*-EVOaffected · semver
- 21.2-EVO and later · before 21.2R3-S6-EVOaffected · semver
- 21.3R1-EVO and later · before 21.3*-EVOaffected · semver
- 21.4-EVO and later · before 21.4R3-S3-EVOaffected · semver
- 22.1-EVO and later · before 22.1R3-S4-EVOaffected · semver
- 22.2-EVO and later · before 22.2R3-S3-EVOaffected · semver
- 22.3-EVO and later · before 22.3R2-S2-EVO, 22.3R3-EVOaffected · semver
- 22.4-EVO and later · before 22.4R2-EVOaffected · semver
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-44190Oct 11, 2023 · Junos OS Evolved: PTX10001, PTX10004, PTX10008, PTX10016: MAC address validation bypass vulnerability21Monitor
- ← EarlierCVE-2023-44195Oct 12, 2023 · Junos OS Evolved: Packets which are not destined to the router can reach the RE21Monitor
- Later →CVE-2024-21602Jan 11, 2024 · Junos OS Evolved: ACX7024, ACX7100-32C and ACX7100-48L: Traffic stops when a specific IPv4 UDP packet is received by the RE30Monitor
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 | 20.4R3-S8-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 21.1*-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 21.2R3-S6-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 21.3*-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 21.4R3-S3-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.1R3-S4-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.2R3-S3-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.3R2-S2-EVO, 22.3R3-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.4R2-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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment 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
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.