dbcve.org
JunosOperating system · Juniper

CVE-2024-47491

MEDIUM · 5.9 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 21.4 or later.
See remediation →
68/100
Remediation priority · Elevated
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 the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based, unauthenticated attacker to cause Denial of Service (DoS). When a BGP UPDATE with malformed path attribute is received over an established BGP session, rpd crashes and restarts. Continuous receipt of a BGP UPDATE with a specifically malformed path attribute will create a sustained Denial of Service (DoS) condition for impacted devices. While this issue affects systems running 32-bit and 64-bit systems, the probability of impact on 64-bit system is extremely low.  According to KB25803 https://supportportal.juniper.net/s/article/Junos-How-to-check-if-Junos-OS-is-64-or-32-bit-on-a-router , customers can confirm 32-bit or 64-bit system via the ' show version detail ' command:      lab@router> show version detail| match 32      JUNOS 32-bit kernel Software Suite       lab@router> show version detail| match 64      JUNOS 64-bit kernel Software Suite  This issue affects:  Juniper Networks Junos OS:  * All versions before 21.4R3-S8,  * from 22.2 before 22.2R3-S4,  * from 22.4 before 22.4R3-S3,  * from 23.2 before 23.2R2-S1,  * from 23.4 before 23.4R1-S2, 23.4R2.  Juniper Networks Junos OS Evolved:  * All versions before 21.4R3-S8-EVO, * from 22.2 before 22.2R3-S4-EVO, * from 22.4 before 22.4R3-S3-EVO, * from 23.2 before 23.2R2-S1-EVO, * from 23.4 before 23.4R1-S2-EVO, 23.4R2-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

A vulnerability in Juniper's Routing Protocol Daemon (rpd) allows an unauthenticated, network-based attacker to crash and restart the daemon by sending BGP UPDATE messages containing malformed path attributes over an established BGP session. Repeated exploitation creates a sustained DoS condition. The issue affects specific versions of both Junos OS and Junos OS Evolved, with 32-bit systems at higher risk than 64-bit systems.

MitigationApply the appropriate Junos OS or Junos OS Evolved patch (21.4R3-S8, 22.2R3-S4, 22.4R3-S3, 23.2R2-S1, or 23.4R1-S2/23.4R2) per the version-specific guidance. Additionally, implement BGP route validation and filtering at edge routers to reject malformed BGP updates.

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:< 21.4= 21.4= 22.2= 22.4= 23.2= 23.4
Junos Os EvolvedOperating system
Affected:< 21.4= 21.4= 22.2= 22.4= 23.2= 23.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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. Identify the installed Junos product
    Run 'show version' or 'request system version' to determine if the device runs Junos OS or Junos OS Evolved
    Affected if The device runs either Junos OS or Junos OS Evolved
  2. Check the installed version number
    Run 'show version' and locate the Junos version string (for example, 21.4R1, 22.2R3, 23.4R1)
    Affected if The version matches one of the affected ranges: < 21.4, = 21.4, = 22.2, = 22.4, = 23.2, or = 23.4
  3. Verify if BGP is enabled
    Run 'show bgp summary' or check the configuration with 'show configuration protocols bgp'
    Affected if BGP is configured and an established BGP session exists (the attack requires an established BGP session to send malformed UPDATE messages)
  4. Check the system architecture
    Run 'show version' and look for architecture indicators such as '32-bit' or 'RE (32-bit)' in the output, or consult hardware documentation for the routing engine type
    Affected if The system runs a 32-bit version (32-bit systems face higher risk than 64-bit systems)
  5. Assess BGP session exposure
    Review the BGP peer configuration with 'show configuration protocols bgp' and identify whether peers are from trusted internal networks or external/untrusted sources
    Affected if BGP peers include untrusted or external networks (the attacker only needs an established BGP session, not internal access)

A user is affected if they run Junos OS or Junos OS Evolved with a version matching the affected list AND have BGP enabled with an established session, especially on 32-bit systems exposed to untrusted BGP peers.

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

Apply the appropriate Junos OS or Junos OS Evolved patch (21.4R3-S8, 22.2R3-S4, 22.4R3-S3, 23.2R2-S1, or 23.4R1-S2/23.4R2) per the version-specific guidance. Additionally, implement BGP route validation and filtering at edge routers to reject malformed BGP updates.

Recommended fix High confidence

Upgrade to Junos OS 21.4R3-S8 / 22.2R3-S4 / 22.4R3-S3 / 23.2R2-S1 / 23.4R1-S2 / 23.4R2 or later (or corresponding Junos OS Evolved equivalents)

  1. 1. Identify the current Junos OS version by running: show version
  2. 2. Determine if the system is 32-bit or 64-bit by running: show version detail | match "32-bit|64-bit"
  3. 3. Select the appropriate fixed release based on the current version branch: 21.4R3-S8 or later for 21.4 branch, 22.2R3-S4 or later for 22.2 branch, 22.4R3-S3 or later for 22.4 branch, 23.2R2-S1 or later for 23.2 branch, or 23.4R1-S2/23.4R2 or later for 23.4 branch
  4. 4. Download the appropriate Junos OS upgrade image from the Juniper Networks support portal
  5. 5. Back up the current configuration using: request system configuration rescue save
  6. 6. Upload the upgrade image to the device
  7. 7. Perform the upgrade using: request system software add <package-name> reboot
  8. 8. After reboot, verify the new version with: show version
Caveat Review Juniper release notes for any known compatibility issues; test upgrade in lab environment before deploying to production

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

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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