dbcve.org
JunosOperating system · Juniper

CVE-2024-47504

HIGH · 7.5 CVSS v3.1 Published 2024-10-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Validation of Specified Type of Input vulnerability in the packet forwarding engine (pfe) Juniper Networks Junos OS on SRX5000 Series allows an unauthenticated, network based attacker to cause a Denial of Service (Dos). When a non-clustered SRX5000 device receives a specifically malformed packet this will cause a flowd crash and restart. This issue affects Junos OS: * 22.1 releases 22.1R1 and later before 22.2R3-S5, * 22.3 releases before 22.3R3-S4, * 22.4 releases before 22.4R3-S4, * 23.2 releases before 23.2R2-S2, * 23.4 releases before 23.4R2-S1, * 24.2 releases before 24.2R1-S1, 24.2R2. Please note that the PR does indicate that earlier versions have been fixed as well, but these won't be adversely impacted by this.

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

Improper input validation in the packet forwarding engine (pfe) of Juniper Networks Junos OS on SRX5000 Series allows an unauthenticated, network-based attacker to send a specifically malformed packet that triggers a flowd crash and restart, resulting in Denial of Service.

MitigationUpgrade Junos OS to one of the fixed versions (22.2R3-S5, 22.3R3-S4, 22.4R3-S4, 23.2R2-S2, 23.4R2-S1, or 24.2R1-S1/24.2R2) to remediate this vulnerability. If immediate patching is not possible, consider implementing packet filtering at upstream devices to block potentially malformed traffic.

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:= 22.1= 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
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. Identify the Junos OS version
    Execute 'show version' on the device CLI to retrieve the installed Junos OS release version
    Affected if The version matches one of the affected releases: 22.1, 22.3, 22.4, 23.2, 23.4, or 24.2 series versions
  2. Confirm the device model is SRX5000 Series
    Execute 'show chassis hardware' or 'show version' to identify the hardware model
    Affected if The device is an SRX5000 Series branch (SRX5400, SRX5600, or SRX5800)
  3. Check if flowd service has crashed
    Review system logs with 'show log messages | match flowd' or check for recent flowd process restarts using 'show system processes | match flowd'
    Affected if flowd has crashed or restarted unexpectedly, or crash logs contain flowd-related errors
  4. Inspect PFE (packet forwarding engine) status
    Execute 'show pfe statistics error' or 'show pfe hardware' to examine the PFE subsystem health
    Affected if The PFE reports errors or the pfe process shows abnormal termination history

A user is affected if their SRX5000 device runs a vulnerable Junos OS version (22.1, 22.3, 22.4, 23.2, 23.4, or 24.2) AND shows evidence of flowd crashes or PFE errors matching the malformed packet signature.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to one of the fixed versions (22.2R3-S5, 22.3R3-S4, 22.4R3-S4, 23.2R2-S2, 23.4R2-S1, or 24.2R1-S1/24.2R2) to remediate this vulnerability. If immediate patching is not possible, consider implementing packet filtering at upstream devices to block potentially malformed traffic.

Recommended fix High confidence

Upgrade to 22.2R3-S5 / 22.3R3-S4 / 22.4R3-S4 / 23.2R2-S2 or later (whichever corresponds to your current release branch)

  1. 1. Identify the current Junos OS version running on the SRX5000 Series device using 'show version'
  2. 2. Based on your current version branch, plan upgrade to the minimum fixed release: for 22.1 branch upgrade to 22.2R3-S5 or later, for 22.3 branch upgrade to 22.3R3-S4 or later, for 22.4 branch upgrade to 22.4R3-S4 or later, for 23.2 branch upgrade to 23.2R2-S2 or later
  3. 3. Download the appropriate fixed Junos OS release from the Juniper support portal
  4. 4. Transfer the Junos OS upgrade package to the SRX5000 device
  5. 5. Initiate the upgrade using 'request system software add <package>' command
  6. 6. Reboot the device after upgrade completes using 'request system reboot'
  7. 7. Verify the new version is running with 'show version' and confirm flowd process stability
Caveat Standard Junos OS upgrade best practices apply - schedule maintenance window, backup configuration, and verify compatibility with other connected Juniper devices

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
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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