dbcve.org
JunosOperating system · Juniper

CVE-2023-36832

HIGH · 7.5 CVSS v3.1 Published 2023-07-14
Fix available
A fix is available. Upgrade to 19.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An Improper Handling of Exceptional Conditions vulnerability in packet processing of Juniper Networks Junos OS on MX Series allows an unauthenticated network-based attacker to send specific packets to an Aggregated Multiservices (AMS) interface on the device, causing the packet forwarding engine (PFE) to crash, resulting in a Denial of Service (DoS). Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. This issue is only triggered by packets destined to a local-interface via a service-interface (AMS). AMS is only supported on the MS-MPC, MS-MIC, and MX-SPC3 cards. This issue is not experienced on other types of interfaces or configurations. Additionally, transit traffic does not trigger this issue. This issue affects Juniper Networks Junos OS on MX Series: All versions prior to 19.1R3-S10; 19.2 versions prior to 19.2R3-S7; 19.3 versions prior to 19.3R3-S8; 19.4 versions prior to 19.4R3-S12; 20.2 versions prior to 20.2R3-S8; 20.4 versions prior to 20.4R3-S7; 21.1 versions prior to 21.1R3-S5; 21.2 versions prior to 21.2R3-S5; 21.3 versions prior to 21.3R3-S4; 21.4 versions prior to 21.4R3-S3; 22.1 versions prior to 22.1R3-S2; 22.2 versions prior to 22.2R3; 22.3 versions prior to 22.3R2-S1, 22.3R3; 22.4 versions prior to 22.4R1-S2, 22.4R2.

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 confidence

An improper handling of exceptional conditions vulnerability in packet processing of Juniper Networks Junos OS on MX Series allows an unauthenticated network-based attacker to send specific packets to an Aggregated Multiservices (AMS) interface, causing the packet forwarding engine (PFE) to crash. Only traffic destined to a local-interface via a service-interface (AMS) on MS-MPC, MS-MIC, or MX-SPC3 cards triggers this issue.

MitigationUpgrade Junos OS to a fixed version as specified in the vendor advisory (22.3R2-S1/22.3R3 or later for 22.x branch, 22.4R1-S2/22.4R2 or later for 22.4 branch, or the corresponding fixed versions for earlier branches).

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
JunosOperating system
Affected:< 19.1= 19.1= 19.2= 19.3= 19.4= 20.2= 20.4= 21.1= 21.2= 21.3= 21.4= 22.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is MX Series
    Run 'show chassis hardware' or 'show system information' to verify the device model is an MX Series router
    Affected if Device is not an MX Series (vulnerability only affects MX Series)
  2. Check Junos OS version
    Run 'show version' to identify the installed Junos OS version
    Affected if Version matches any of the affected versions: 19.1, 19.2, 19.3, 19.4, 20.2, 20.4, 21.1, 21.2, 21.3, 21.4, or 22.1, or is earlier than 19.1
  3. Verify presence of service cards
    Run 'show chassis hardware' and look for MS-MPC, MS-MIC, or MX-SPC3 line cards in the hardware inventory
    Affected if None of these service cards (MS-MPC, MS-MIC, MX-SPC3) are present in the system
  4. Check for AMS interface configuration
    Run 'show configuration interfaces ams*' or search for 'ams' in the active configuration to see if Aggregated Multiservices interfaces are configured
    Affected if No AMS interfaces are configured in the system
  5. Verify AMS interface is bound to service cards
    Run 'show services interface' or 'show ams interface' to confirm AMS interfaces are bound to MS-MPC, MS-MIC, or MX-SPC3 service interfaces
    Affected if AMS interfaces are not bound to the vulnerable service card types

Environment is affected if it is an MX Series router running a vulnerable Junos version (19.1 through 22.1), has MS-MPC/MS-MIC/MX-SPC3 service cards present, and has AMS interfaces configured and bound to those service cards.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 19.1 or later
Fixed in 19.1
Interim mitigation

Upgrade Junos OS to a fixed version as specified in the vendor advisory (22.3R2-S1/22.3R3 or later for 22.x branch, 22.4R1-S2/22.4R2 or later for 22.4 branch, or the corresponding fixed versions for earlier branches).

Recommended fix High confidence

Upgrade to 19.1R3-S10 or later for 19.1.x; 19.2R3-S7 or later for 19.2.x; 19.3R3-S8 or later for 19.3.x; or ideally the latest stable release (22.4R2 or later if hardware supports it)

  1. 1. Identify the current Junos OS version running on the MX Series device using 'show version' command
  2. 2. Identify if the device is using AMS (Aggregated Multiservices) interfaces on MS-MPC, MS-MIC, or MX-SPC3 cards using 'show interfaces ams' or 'show chassis hardware'
  3. 3. If AMS is in use, plan for upgrade to a fixed release as per the version matrix provided
  4. 4. Schedule a maintenance window for the upgrade process
  5. 5. Download the appropriate fixed Junos OS release from Juniper Networks (e.g., 19.1R3-S10, 19.2R3-S7, 19.3R3-S8, or later)
  6. 6. Upload the new Junos OS image to the device using 'request system software add' command
  7. 7. Reboot the device to apply the new software version using 'request system reboot'
  8. 8. After reboot, verify the new version is running with 'show version' and confirm AMS interfaces are operational with 'show interfaces ams'
Caveat Review Juniper MX Series release notes for any configuration or feature changes between current and target version; some legacy features may be deprecated in newer releases

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36832 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36832 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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