dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-47509

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 21.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 PFE management daemon (evo-pfemand) of Juniper Networks Junos OS Evolved allows an authenticated, network-based attacker to cause an FPC crash leading to a Denial of Service (DoS).When specific SNMP GET operations or specific low-priviledged CLI commands are executed, a GUID resource leak will occur, eventually leading to exhaustion and resulting in FPCs to hang. Affected FPCs need to be manually restarted to recover. GUID exhaustion will trigger a syslog message like one of the following: evo-pfemand[<pid>]: get_next_guid: Ran out of Guid Space ... evo-aftmand-zx[<pid>]: get_next_guid: Ran out of Guid Space ... The leak can be monitored by running the following command and taking note of the values in the rightmost column labeled Guids: user@host> show platform application-info allocations app evo-pfemand/evo-pfemand In case one or more of these values are constantly increasing the leak is happening. This issue affects Junos OS Evolved: * All versions before 21.4R2-EVO, * 22.1 versions before 22.1R2-EVO. Please note that this issue is similar to, but different from CVE-2024-47505 and CVE-2024-47508.

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 GUID resource leak in the PFE management daemon (evo-pfemand) of Juniper Networks Junos OS Evolved allows an authenticated, network-based attacker to cause GUID exhaustion through specific SNMP GET operations or low-privileged CLI commands. The leak progressively consumes GUID resources until the system hits a limit, causing FPCs to hang or crash and requiring manual restart for recovery.

MitigationApply the vendor-provided software update (21.4R2-EVO or 22.1R2-EVO or later) to address the GUID leak; until then, monitor for syslog messages indicating 'Ran out of Guid Space' and track allocations via 'show platform application-info allocations' command.

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.1

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Evolved version
    Run 'show version' or 'cat /etc/version' to obtain the installed version
    Affected if The version is less than 21.4, equals 21.4, or equals 22.1 (fixed versions are 21.4R2-EVO and 22.1R2-EVO or later)
  2. Search for GUID exhaustion syslog messages
    Run 'show log messages | match "Ran out of Guid Space"' or review system logs for this specific error string
    Affected if Any 'Ran out of Guid Space' messages appear in the logs
  3. Check GUID allocations via application-info
    Run the CLI command 'show platform application-info allocations' and review the GUID allocation statistics
    Affected if GUID allocations show unusual growth or approach the system limit
  4. Verify FPC status for hangs or crashes
    Run 'show chassis fpc' or 'show chassis fpc pic-status' to check for FPCs that are offline, hung, or in crash state
    Affected if Any FPCs show as offline, hung, or crashed with no obvious hardware cause
  5. Check evo-pfemand daemon status
    Run 'show system processes' or 'ps aux | grep evo-pfemand' to verify the PFE management daemon is running
    Affected if The daemon is running (necessary but not sufficient alone - combines with other indicators)

A system is affected if it runs a vulnerable Junos OS Evolved version (21.4, 22.1, or any version below 21.4) AND shows GUID exhaustion symptoms such as 'Ran out of Guid Space' syslog messages, high GUID allocations, or FPC instability.

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 vendor-provided software update (21.4R2-EVO or 22.1R2-EVO or later) to address the GUID leak; until then, monitor for syslog messages indicating 'Ran out of Guid Space' and track allocations via 'show platform application-info allocations' command.

Recommended fix High confidence

21.4R2-EVO or later, or 22.1R2-EVO or later

  1. Upgrade Junos OS Evolved to version 21.4R2-EVO or later for the 21.4 track
  2. If running 22.1.x, upgrade to version 22.1R2-EVO or later
  3. After upgrade, verify the fix by running 'show platform application-info allocations app evo-pfemand/evo-pfemand' and checking that GUID values are stable
  4. Monitor syslog for 'get_next_guid: Ran out of Guid Space' messages to confirm the leak is resolved
  5. If FPCs are already hung, manually restart the affected FPCs after applying the upgrade
Caveat Standard Junos OS Evolved upgrade considerations apply - review release notes for compatibility and ensure proper configuration backup before upgrading

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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