# CVE-2024-30401: Junos OS: MX Series and EX9200-15C: Stack-based buffer overflow in aftman

> An attacker can trigger a stack-based buffer overflow in the aftman process, causing a reboot of the FPC on affected Juniper MX and EX9200 devices.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-pqmg-f829-g3ww

## What is CVE-2024-30401?

CVE-2024-30401 is a high-severity memory corruption vulnerability in Juniper Junos, published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Out-of-bounds Read vulnerability in the advanced forwarding management process aftman of Juniper Networks Junos OS on MX Series with MPC10E, MPC11, MX10K-LC9600 line cards, MX304, and EX9200-15C, may allow an attacker to exploit a stack-based buffer overflow, leading to a reboot of the FPC.

Through code review, it was determined that the interface definition code for aftman could read beyond a buffer boundary, leading to a stack-based buffer overflow.
This issue affects Junos OS on MX Series and EX9200-15C:

  *  from 21.2 before 21.2R3-S1, 
  *  from 21.4 before 21.4R3, 
  *  from 22.1 before 22.1R2, 
  *  from 22.2 before 22.2R2; 

This issue does not affect:

  *  versions of Junos OS prior to 20.3R1;
  *  any version of Junos OS 20.4.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2024-30401 being exploited?

There is no known exploitation of CVE-2024-30401 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-30401 and fix it if it is affected.

What it is: CVE-2024-30401 is a high-severity memory corruption vulnerability in Juniper Junos, published on 12 Apr 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-30401 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-30401/ (Markdown: https://insights.sbomify.com/CVE-2024-30401/index.md)
```

## Sources

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

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