# CVE-2024-47494: Junos OS: Due to a race condition AgentD process causes a memory corruption and FPC reset

> A race condition in Junos OS AgentD allows attackers to cause memory corruption and FPC crashes, resulting in denial of service.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/AU:Y/R:A/RE:L/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2024
- **Updated:** 11 Oct 2024
- **Also known as:** GHSA-f3wp-gx52-q6g2

## What is CVE-2024-47494?

CVE-2024-47494 is a high-severity vulnerability in Juniper Junos, published on 11 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in the AgentD process of Juniper Networks Junos OS allows an attacker who is already causing impact to established sessions which generates counter changes picked up by the AgentD process during telemetry polling, to move the AgentD process into a state where AgentD attempts to reap an already destroyed sensor. This reaping attempt then leads to memory corruption causing the FPC to crash which is a Denial of Service (DoS).

The FPC will recover automatically without user intervention after the crash.
This issue affects Junos OS: 

  *  All versions before 21.4R3-S9
  *  From 22.2 before 22.2R3-S5,
  *  From 22.3 before 22.3R3-S4,
  *  From 22.4 before 22.4R3-S3,
  *  From 23.2 before 23.2R2-S2,
  *  From 23.4 before 23.4R2.

This issue does not affect Junos OS Evolved.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2024-47494?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2024-47494?

No fix has been published for CVE-2024-47494 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-47494 being exploited?

There is no known exploitation of CVE-2024-47494 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47494 and fix it if it is affected.

What it is: CVE-2024-47494 is a high-severity vulnerability in Juniper Junos, published on 11 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47494 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47494/ (Markdown: https://insights.sbomify.com/CVE-2024-47494/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47494
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47494
- OSV: https://osv.dev/vulnerability/CVE-2024-47494

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47494/
Summaries are generated and may contain mistakes; the official description above is the record.