CVE-2023-22401
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn Improper Validation of Array Index vulnerability in the Advanced Forwarding Toolkit Manager daemon (aftmand) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). On the PTX10008 and PTX10016 platforms running Junos OS or Junos OS Evolved, when a specific SNMP MIB is queried this will cause a PFE crash and the FPC will go offline and not automatically recover. A system restart is required to get the affected FPC in an operational state again. This issue affects: Juniper Networks Junos OS 22.1 version 22.1R2 and later versions; 22.1 versions prior to 22.1R3; 22.2 versions prior to 22.2R2. Juniper Networks Junos OS Evolved 21.3-EVO version 21.3R3-EVO and later versions; 21.4-EVO version 21.4R1-S2-EVO, 21.4R2-EVO and later versions prior to 21.4R2-S1-EVO; 22.1-EVO version 22.1R2-EVO and later versions prior to 22.1R3-EVO; 22.2-EVO versions prior to 22.2R1-S1-EVO, 22.2R2-EVO.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceImproper validation of array index in the Advanced Forwarding Toolkit Manager daemon (aftmand) allows unauthenticated network attackers to cause denial of service by querying a specific SNMP MIB on PTX10008 and PTX10016 platforms, resulting in PFE crash and FPC going offline with no auto-recovery.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 22.1= 22.2= 21.3= 21.4= 22.1= 22.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the hardware platformRun 'show chassis hardware' or check the model name via 'show system information'Affected if The platform is NOT PTX10008 or PTX10016 (vulnerability only affects these specific models)
-
Check Junos OS versionRun 'show version' or 'show version detail' to display the installed Junos versionAffected if The version matches 22.1 or 22.2 (for Junos) OR 21.3, 21.4, 22.1, 22.2 (for Junos OS Evolved)
-
Verify SNMP is configuredRun 'show configuration snmp' to view SNMP configurationAffected if SNMP is enabled and accessible from untrusted networks (the flaw is triggered by querying a specific SNMP MIB)
-
Confirm aftmand daemon statusRun 'show system processes daemon' or check process list for aftmandAffected if The Advanced Forwarding Toolkit Manager daemon (aftmand) is running (required for the vulnerable code path to be reachable)
Device is affected if it is a PTX10008 or PTX10016 running a vulnerable Junos/Evolved version (22.1, 22.2 for Junos or 21.3, 21.4, 22.1, 22.2 for Junos Evolved) with SNMP access enabled from the network where the attacker resides.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply vendor-supplied Junos OS/Evolved patches (22.1R3, 22.2R2, 21.4R2-S1-EVO, 22.1R3-EVO, 22.2R1-S1-EVO or later as appropriate) to fixed versions. Consider SNMP access controls as interim mitigation.
Junos OS: 22.1R3 or 22.2R2; Junos OS Evolved: 21.4R2-S1-EVO, 22.1R3-EVO, or 22.2R1-S1-EVO/22.2R2-EVO
- 1. Identify the exact Junos OS or Junos OS Evolved version currently running on the affected PTX10008 or PTX10016 devices
- 2. For Junos OS: upgrade to version 22.1R3 or later, or 22.2R2 or later
- 3. For Junos OS Evolved 21.4-EVO: upgrade to 21.4R2-S1-EVO or later
- 4. For Junos OS Evolved 22.1-EVO: upgrade to 22.1R3-EVO or later
- 5. For Junos OS Evolved 22.2-EVO: upgrade to 22.2R1-S1-EVO or later, or 22.2R2-EVO or later
- 6. After upgrade, verify the Advanced Forwarding Toolkit Manager daemon (aftmand) is running properly
- 7. Test SNMP MIB queries on the affected platforms to confirm the vulnerability is remediated
- 8. If an FPC goes offline after the upgrade, restart the device as needed to restore full functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22401 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data