dbcve.org
JunosOperating system · Juniper

CVE-2024-47503

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 21.4 or later.
See remediation →
70/100
Remediation priority · Elevated
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 Check for Unusual or Exceptional Conditions vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX4600 and SRX5000 Series allows an unauthenticated and logically adjacent attacker to cause a Denial-of-Service (DoS). If in a multicast scenario a sequence of specific PIM packets is received, this will cause a flowd crash and restart, which leads to momentary service interruption. This issue affects Junos OS on SRX 4600 and SRX 5000 Series: * All versions before 21.4R3-S9, * 22.2 versions before 22.2R3-S5, * 22.3 versions before 22.3R3-S4, * 22.4 versions before 22.4R3-S4, * 23.2 versions before 23.2R2-S2, * 23.4 versions before 23.4R2,  * 24.2 versions before 24.2R1-S1, 24.2R2.

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 the flow processing daemon (flowd) of Juniper Junos OS on SRX4600 and SRX5000 Series allows an unauthenticated adjacent attacker to cause DoS by sending specific PIM packets in a multicast scenario, triggering improper error handling that leads to flowd crash and restart.

MitigationUpgrade Junos OS to the specified patched versions (21.4R3-S9, 22.2R3-S5, 22.3R3-S4, 22.4R3-S4, 23.2R2-S2, 23.4R2, 24.2R1-S1 or 24.2R2). If upgrade is not immediately feasible, consider isolating PIM traffic or restricting logical adjacency.

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.3= 22.4= 23.2= 23.4= 24.2

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/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. Identify device model
    Run 'show chassis hardware' or check the device model to confirm it is an SRX4600 or SRX5000 Series device
    Affected if Device is SRX4600 or SRX5000 Series
  2. Check Junos OS version
    Run 'show version' to obtain the installed Junos OS version and compare it to the affected ranges: <21.4, 21.4, 22.2, 22.3, 22.4, 23.2, 23.4, 24.2
    Affected if Installed version matches any of the affected versions listed
  3. Verify PIM is enabled
    Run 'show protocols pim' or check the configuration under 'protocols pim' to determine if Protocol Independent Multicast is configured and active
    Affected if PIM is enabled and multicast routing is configured
  4. Check flowd crash history
    Run 'show system crash' or review /var/log/messages for recent flowd process restarts, particularly those correlating with multicast/PIM traffic events
    Affected if flowd has crashed or restarted recently and PIM is in use

Device is affected if it is an SRX4600 or SRX5000 Series running a vulnerable Junos version AND PIM multicast is enabled, making it susceptible to flowd crash from malicious PIM packets.

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

Upgrade Junos OS to the specified patched versions (21.4R3-S9, 22.2R3-S5, 22.3R3-S4, 22.4R3-S4, 23.2R2-S2, 23.4R2, 24.2R1-S1 or 24.2R2). If upgrade is not immediately feasible, consider isolating PIM traffic or restricting logical adjacency.

Recommended fix High confidence

Upgrade to the latest fixed version in your current branch: 21.4R3-S9+, 22.2R3-S5+, 22.3R3-S4+, 22.4R3-S4+, 23.2R2-S2+, 23.4R2+, or 24.2R2 (for 24.2 branch)

  1. 1. Identify the current Junos OS version running on the SRX4600 or SRX5000 Series device using 'show version'
  2. 2. Determine which version branch you are currently on (21.4, 22.2, 22.3, 22.4, 23.2, 23.4, or 24.2)
  3. 3. Download the appropriate fixed version for your branch from the Juniper Networks support portal: for 21.4 branch use 21.4R3-S9 or later, for 22.2 use 22.2R3-S5 or later, for 22.3 use 22.3R3-S4 or later, for 22.4 use 22.4R3-S4 or later, for 23.2 use 23.2R2-S2 or later, for 23.4 use 23.4R2 or later, for 24.2 use 24.2R1-S1 or 24.2R2
  4. 4. Upload the Junos OS upgrade package to the device using 'file copy' or similar method
  5. 5. Install the upgrade using 'request system software add <package-name>' command
  6. 6. Reboot the device to complete the installation using 'request system reboot'
  7. 7. After reboot, verify the new version is running with 'show version' and confirm the fix is applied
Caveat Standard Junos OS upgrade precautions apply - plan for maintenance window as device will reboot; 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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