# CVE-2024-30405: Denial of service in Junos OS

> Attackers can cause a sustained denial of service on Juniper SRX 5000 devices by sending crafted packets when Application Layer Gateways are enabled.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L`)
- **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:** 12 Aug 2024
- **Also known as:** GHSA-6gj8-fxh3-h3j9

## What is CVE-2024-30405?

CVE-2024-30405 is a high-severity denial of service 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 Incorrect Calculation of Buffer Size vulnerability in Juniper Networks Junos OS SRX 5000 Series devices using SPC2 line cards while ALGs are enabled allows an attacker sending specific crafted packets to cause a transit traffic Denial of Service (DoS).

Continued receipt and processing of these specific packets will sustain the Denial of Service condition.

This issue affects:
Juniper Networks Junos OS SRX 5000 Series with SPC2 with ALGs enabled.
  *  All versions earlier than 21.2R3-S7;
  *  21.4 versions earlier than 21.4R3-S6;
  *  22.1 versions earlier than 22.1R3-S5;
  *  22.2 versions earlier than 22.2R3-S3;
  *  22.3 versions earlier than 22.3R3-S2;
  *  22.4 versions earlier than 22.4R3;
  *  23.2 versions earlier than 23.2R2.

Weakness: CWE-131 (Incorrect Calculation of Buffer Size)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2024-30405 being exploited?

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

What it is: CVE-2024-30405 is a high-severity denial of service 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-30405 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-30405/ (Markdown: https://insights.sbomify.com/CVE-2024-30405/index.md)
```

## Sources

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

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