dbcve.org
JunosOperating system · Juniper

CVE-2023-44197

HIGH · 7.5 CVSS v3.1 Published 2023-10-13
Fix available
A fix is available. Upgrade to 20.4 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 Out-of-Bounds Write vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). On all Junos OS and Junos OS Evolved devices an rpd crash and restart can occur while processing BGP route updates received over an established BGP session. This specific issue is observed for BGP routes learned via a peer which is configured with a BGP import policy that has hundreds of terms matching IPv4 and/or IPv6 prefixes. This issue affects Juniper Networks Junos OS: * All versions prior to 20.4R3-S8; * 21.1 version 21.1R1 and later versions; * 21.2 versions prior to 21.2R3-S2; * 21.3 versions prior to 21.3R3-S5; * 21.4 versions prior to 21.4R2-S1, 21.4R3-S5. 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 versions; * 21.2-EVO versions prior to 21.2R3-S2-EVO; * 21.3-EVO version 21.3R1-EVO and later versions; * 21.4-EVO versions prior to 21.4R2-S1-EVO, 21.4R3-S5-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 confidence

An out-of-bounds write vulnerability in the Routing Protocol Daemon (rpd) of Juniper Junos OS and Junos OS Evolved allows an unauthenticated attacker to crash rpd by sending specially crafted BGP route updates over an established BGP session when the peer's import policy contains hundreds of terms matching IPv4/IPv6 prefixes, causing a denial of service.

MitigationApply the vendor-provided patches for affected Junos OS/Evolved versions. As an interim measure, review and simplify BGP import policies to reduce the number of terms, and consider implementing BGP route filtering or prefix limits on untrusted peers.

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:< 20.4= 20.4= 21.1= 21.2= 21.3= 21.4
Junos Os EvolvedOperating system
Affected:< 20.4= 20.4= 21.1= 21.2= 21.3= 21.4

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. Check Junos OS version
    Run 'show version' or 'show version detail' to display the installed Junos OS version
    Affected if Version matches < 20.4, 20.4, 21.1, 21.2, 21.3, or 21.4
  2. Verify BGP is configured
    Run 'show configuration protocols bgp' to view BGP configuration and 'show bgp summary' to see active BGP peers
    Affected if BGP is configured and there are established BGP peers
  3. Inspect BGP import policies
    Run 'show configuration protocols bgp | display set' or access the policy structure via 'edit policy-options policy-statement <policy-name>' to count the number of terms in each import policy applied to BGP peers
    Affected if Any BGP peer has an import policy containing hundreds of terms that match IPv4/IPv6 prefixes

You are affected if your Junos version is 20.4, 21.1, 21.2, 21.3, or 21.4 (or any version below 20.4) AND you have BGP peers with complex import policies containing hundreds of terms.

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 20.4 or later
Fixed in 20.4
Interim mitigation

Apply the vendor-provided patches for affected Junos OS/Evolved versions. As an interim measure, review and simplify BGP import policies to reduce the number of terms, and consider implementing BGP route filtering or prefix limits on untrusted peers.

Recommended fix High confidence

20.4R3-S8 or later (20.4 branch), 21.2R3-S2 or later (21.2 branch), 21.3R3-S5 or later (21.3 branch), 21.4R2-S1/21.4R3-S5 or later (21.4 branch)

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Based on the current version branch, upgrade to one of the fixed releases:
  3. - For 20.4 branch: upgrade to 20.4R3-S8 or later
  4. - For 21.1 branch: upgrade to 21.1R3-S10 or later 21.1 version
  5. - For 21.2 branch: upgrade to 21.2R3-S2 or later
  6. - For 21.3 branch: upgrade to 21.3R3-S5 or later
  7. - For 21.4 branch: upgrade to 21.4R2-S1 or 21.4R3-S5 or later
  8. 3. Download the appropriate upgrade image from the Juniper Networks support portal
Caveat Standard Junos upgrade precautions apply - verify compatibility with other installed modules and review upgrade guide; ensure configuration backup before upgrade

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44197 — 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-44197 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