Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-44186Junos OS and Junos OS Evolved: RPD crash when attempting to send a very long AS PATH to a non-4-byte-AS capable BGP neighbor

Description

An Improper Handling of Exceptional Conditions vulnerability in AS PATH processing of Juniper Networks Junos OS and Junos OS Evolved allows an attacker to send a BGP update message with an AS PATH containing a large number of 4-byte ASes, leading to a Denial of Service (DoS). Continued receipt and processing of these BGP updates will create a sustained Denial of Service (DoS) condition. This issue is hit when the router has Non-Stop Routing (NSR) enabled, has a non-4-byte-AS capable BGP neighbor, receives a BGP update message with a prefix that includes a long AS PATH containing large number of 4-byte ASes, and has to advertise the prefix towards the non-4-byte-AS capable BGP neighbor. Note: NSR is not supported on the SRX Series and is therefore not affected by this vulnerability. This issue affects: Juniper Networks Junos OS: * All versions prior to 20.4R3-S8; * 21.1 versions 21.1R1 and later; * 21.2 versions prior to 21.2R3-S6; * 21.3 versions prior to 21.3R3-S5; * 21.4 versions prior to 21.4R3-S5; * 22.1 versions prior to 22.1R3-S4; * 22.2 versions prior to 22.2R3-S2; * 22.3 versions prior to 22.3R2-S2, 22.3R3-S1; * 22.4 versions prior to 22.4R2-S1, 22.4R3. Juniper Networks Junos OS Evolved * All versions prior to 20.4R3-S8-EVO; * 21.1 versions 21.1R1-EVO and later; * 21.2 versions prior to 21.2R3-S6-EVO; * 21.3 versions prior to 21.3R3-S5-EVO; * 21.4 versions prior to 21.4R3-S5-EVO; * 22.1 versions prior to 22.1R3-S4-EVO; * 22.2 versions prior to 22.2R3-S2-EVO; * 22.3 versions prior to 22.3R2-S2-EVO, 22.3R3-S1-EVO; * 22.4 versions prior to 22.4R2-S1-EVO, 22.4R3-EVO.

Timeline

  1. ID reserved

    By juniper

  2. · 15 days later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-44186, by who scored it
Scored byCVSSScoreVector
juniperCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.64% · top 48% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Juniper Networks · Junos OS

    • affected < 20.4R3-S8
    • affected 21.1R1 – < 21.1*
    • affected 21.2 – < 21.2R3-S6
    • affected 21.3 – < 21.3R3-S5
    • affected 21.4 – < 21.4R3-S5
    • affected 22.1 – < 22.1R3-S4
    • affected 22.2 – < 22.2R3-S2
    • affected 22.3 – < 22.3R2-S2, 22.3R3-S1
    • affected 22.4 – < 22.4R2-S1, 22.4R3
  • Juniper Networks · Junos OS Evolved

    • affected < 20.4R3-S8-EVO
    • affected 21.1 – < 21.1*-EVO
    • affected 21.2 – < 21.2R3-S6-EVO
    • affected 21.3 – < 21.3R3-S5-EVO
    • affected 21.4 – < 21.4R3-S5-EVO
    • affected 22.1 – < 22.1R3-S4-EVO
    • affected 22.2 – < 22.2R3-S2-EVO
    • affected 22.3 – < 22.3R2-S2-EVO, 22.3R3-S1-EVO
    • affected 22.4 – < 22.4R2-S1-EVO, 22.4R3-EVO

What to do

Solution: The following software releases have been updated to resolve this specific issue: Junos OS: 20.4R3-S8, 21.2R3-S6, 21.3R3-S5, 21.4R3-S5, 22.1R3-S4, 22.2R3-S2, 22.3R2-S2, 22.3R3-S1, 22.4R2-S1, 22.4R3, 23.2R1, and all subsequent releases. Junos OS Evolved: 20.4R3-S8-EVO, 21.2R3-S6-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S2-EVO, 22.3R2-S2-EVO, 22.3R3-S1-EVO, 22.4R2-S1-EVO, 22.4R3-EVO, 23.2R1-EVO, and all subsequent releases.

Workaround: Current operational and security best practices, such as limiting the AS PATH length, should mitigate risk of this issue. Below is an example configuration to limit AS PATH to 30 entries: set groups BASE-POLICY policy-options policy-statement MaxAS-Limit-30 term more-than-30 from protocol bgp set groups BASE-POLICY policy-options policy-statement MaxAS-Limit-30 term more-than-30 from as-path 31as set groups BASE-POLICY policy-options policy-statement MaxAS-Limit-30 term more-than-30 then reject set groups BASE-POLICY policy-options policy-statement MaxAS-Limit-30 then accept set groups BASE-POLICY policy-options policy-statement Customer-IN term MaxAS-Limit from policy MaxAS-Limit-30 set groups BASE-BGP protocols bgp group <*-CUSTOMER> import Customer-IN set groups BASE-PREFIX-LISTS policy-options as-path 31as ".{31,}"

Exploitation: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-44186 badge
[![CVE-2023-44186](https://cveledger.app/badge/CVE-2023-44186.svg)](https://cveledger.app/cve/CVE-2023-44186)

Record last updated .