# CVE-2024-21591: Junos OS: SRX Series and EX Series: Security Vulnerability in J-web allows a preAuth Remote Code Execution

> Unauthenticated attackers can achieve remote code execution and root privileges on Juniper SRX and EX devices via an out-of-bounds write in J-Web.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2024
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-j7xq-gvq8-pr7m

## What is CVE-2024-21591?

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

### Official description

An Out-of-bounds Write vulnerability in J-Web of Juniper Networks Junos OS on SRX Series and EX Series allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS), or Remote Code Execution (RCE) and obtain root privileges on the device.

This issue is caused by use of an insecure function allowing an attacker to overwrite arbitrary memory.

This issue affects Juniper Networks Junos OS SRX Series and EX Series:

  *  Junos OS versions earlier than 20.4R3-S9;
  *  Junos OS 21.2 versions earlier than 21.2R3-S7;
  *  Junos OS 21.3 versions earlier than 21.3R3-S5;
  *  Junos OS 21.4 versions earlier than 21.4R3-S5;
  *  Junos OS 22.1 versions earlier than 22.1R3-S4;
  *  Junos OS 22.2 versions earlier than 22.2R3-S3;
  *  Junos OS 22.3 versions earlier than 22.3R3-S2;
  *  Junos OS 22.4 versions earlier than 22.4R2-S2, 22.4R3.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2024-21591 being exploited?

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

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

## Sources

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

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