dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-47502

HIGH · 7.5 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 21.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 Allocation of Resources Without Limits or Throttling vulnerability in the kernel of Juniper Networks Junos OS Evolved allows an unauthenticated, network based attacker to cause a Denial of Service (DoS). In specific cases the state of TCP sessions that are terminated is not cleared, which over time leads to an exhaustion of resources, preventing new connections to the control plane from being established. A continuously increasing number of connections shown by: user@host > show system connections is indicative of the problem. To recover the respective RE needs to be restarted manually. This issue only affects IPv4 but does not affect IPv6. This issue only affects TCP sessions established in-band (over an interface on an FPC) but not out-of-band (over the management ethernet port on the routing-engine). This issue affects Junos OS Evolved:  * All versions before 21.4R3-S9-EVO, * 22.2 versions before 22.2R3-S4-EVO, * 22.4 version before 22.4R3-S3-EVO, * 23.2 versions before 23.2R2-S1-EVO, * 23.4 versions before 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 resource exhaustion vulnerability in Juniper Junos OS Evolved kernel allows unauthenticated network attackers to cause DoS by exhausting TCP session state resources. When TCP sessions are terminated in specific cases, their state is not cleared, causing accumulation that prevents new control plane connections.

MitigationApply the appropriate Junos OS Evolved software update (21.4R3-S9-EVO, 22.2R3-S4-EVO, 22.4R3-S3-EVO, 23.2R2-S1-EVO, or 23.4R2-EVO or later) to the affected devices.

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
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
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 Junos OS Evolved version
    Run 'show version' or 'show version invoke-on all-routing-engines' to display the installed software version
    Affected if The version displayed is less than 21.4, or exactly 21.4, 22.2, 22.4, 23.2, or 23.4 (including sub-versions like 21.4R1, 22.2R1, etc.)
  2. Confirm the device runs Junos OS Evolved
    Verify the software variant is 'Junos OS Evolved' and not standard Junos OS, using the 'show version' output which displays the OS name
    Affected if The device runs Junos OS Evolved and the version matches the affected list
  3. Check for TCP session accumulation symptoms
    Monitor control plane connection capacity using 'show system connections' or review kernel memory statistics for TCP session table growth
    Affected if The device shows abnormal TCP session state accumulation or inability to establish new control plane connections
  4. Review system logs for resource exhaustion events
    Examine /var/log/messages or use 'show log messages' for entries indicating TCP connection failures or resource limits
    Affected if Logs show TCP session creation failures or control plane connection rejections

A user is affected if their Juniper device runs Junos OS Evolved with a version matching 21.4, 22.2, 22.4, 23.2, 23.4, or any version below 21.4, and exhibits symptoms of TCP session state exhaustion preventing new control plane connections.

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 Evolved software update (21.4R3-S9-EVO, 22.2R3-S4-EVO, 22.4R3-S3-EVO, 23.2R2-S1-EVO, or 23.4R2-EVO or later) to the affected devices.

Recommended fix High confidence

21.4R3-S9-EVO, 22.2R3-S4-EVO, 22.4R3-S3-EVO, 23.2R2-S1-EVO, or 23.4R2-EVO (or later)

  1. 1. Identify the current Junos OS Evolved version using 'show version' command
  2. 2. Review the upgrade path for your current version in Juniper's documentation
  3. 3. Download the appropriate fixed release: 21.4R3-S9-EVO or later, 22.2R3-S4-EVO or later, 22.4R3-S3-EVO or later, 23.2R2-S1-EVO or later, or 23.4R2-EVO or later
  4. 4. Schedule a maintenance window as the upgrade will require a system reboot
  5. 5. Upload the new Junos OS Evolved package to the device using 'request system software add <package>'
  6. 6. After installation, reboot the device using 'request system reboot'
  7. 7. Verify the new version is running with 'show version'
  8. 8. Monitor 'show system connections' to confirm TCP session cleanup is now functioning properly
Caveat Standard Junos OS Evolved upgrade considerations apply - ensure compatibility with existing network configuration and review release notes for any behavioral changes

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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