dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-47508

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 21.2 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.2R3-S8-EVO, * 21.3 versions before 21.3R3-EVO; * 21.4 versions before 22.1R2-EVO, * 22.1 versions before 22.1R1-S1-EVO, 22.1R2-EVO. Please note that this issue is similar to, but different from CVE-2024-47505 and CVE-2024-47509.

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 vulnerability exists in the PFE management daemon (evo-pfemand) of Juniper Junos OS Evolved. When authenticated attackers execute specific SNMP GET operations or low-privileged CLI commands, GUIDs are leaked without proper cleanup. This leak accumulates over time, eventually causing GUID exhaustion that leads to FPC (Flexible PIC Concentrator) hangs requiring manual restart.

MitigationApply the vendor-supplied patches (21.2R3-S8-EVO, 21.3R3-EVO, 22.1R2-EVO, or 22.1R1-S1-EVO depending on branch). Monitor for the leak using 'show platform application-info allocations app evo-pfemand/evo-pfemand' and restrict SNMP access until patched.

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.2= 21.2= 21.3= 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. Identify Junos OS Evolved version
    Run 'show version' or 'request system version' to obtain the installed Junos OS Evolved version
    Affected if Version is 21.2, 21.3, 21.4, 22.1, or any version below 21.2
  2. Verify evo-pfemand daemon is running
    Run 'show system processes extensive | match evo-pfemand' or check process status via 'request system process daemon evo-pfemand status'
    Affected if The evo-pfemand process is active on the device
  3. Monitor GUID allocations in evo-pfemand
    Execute 'show platform application-info allocations app evo-pfemand/evo-pfemand' and examine the allocation counts, particularly GUID-related allocations
    Affected if Allocation counts continuously increase or show abnormal growth over time
  4. Check FPC status for hangs
    Run 'show chassis fpc' or 'show platform fpc' to examine Flexible PIC Concentrator status
    Affected if FPC shows as offline, hung, or requires manual restart to recover
  5. Review SNMP access patterns
    Check SNMP configuration with 'show snmp' and review access logs for authenticated SNMP GET operations
    Affected if SNMP is enabled and accessible to untrusted users who could trigger the leak

A device is affected if it runs a vulnerable Junos OS Evolved version (21.2, 21.3, 21.4, 22.1, or <21.2), has the evo-pfemand daemon running, and exhibits GUID allocation growth or FPC hang symptoms.

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.2 or later
Fixed in 21.2
Interim mitigation

Apply the vendor-supplied patches (21.2R3-S8-EVO, 21.3R3-EVO, 22.1R2-EVO, or 22.1R1-S1-EVO depending on branch). Monitor for the leak using 'show platform application-info allocations app evo-pfemand/evo-pfemand' and restrict SNMP access until patched.

Recommended fix High confidence

Upgrade to 21.2R3-S8-EVO, 21.3R3-EVO, or 22.1R2-EVO (or later)

  1. Identify current Junos OS Evolved version using 'show version' command
  2. Plan upgrade to one of the fixed releases: 21.2R3-S8-EVO, 21.3R3-EVO, or 22.1R2-EVO (or later)
  3. Schedule a maintenance window for the upgrade
  4. Back up current configuration using 'request system configuration rescue save'
  5. Upgrade the device using 'request system software add <package>' or appropriate upgrade method
  6. Reboot the device if required by the upgrade process
  7. After upgrade, verify version using 'show version'
  8. Monitor for the GUID exhaustion syslog messages: 'get_next_guid: Ran out of Guid Space'
Caveat Standard Junos OS upgrade precautions apply - review release notes for compatibility and ensure configuration compatibility 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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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