# CVE-2024-30390: Junos OS Evolved: Connection limits is not being enforced while the resp. rate limit is being enforced

> An unauthenticated attacker can cause a limited Denial of Service on the management plane by bypassing connection limits.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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-6w72-x59c-h2c9

## What is CVE-2024-30390?

CVE-2024-30390 is a medium-severity denial of service vulnerability in Juniper Junos Os Evolved, 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 Improper Restriction of Excessive Authentication Attempts vulnerability in Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a limited Denial of Service (DoS) to the management plane.

When an incoming connection was blocked because it exceeded the connections-per-second rate-limit, the system doesn't consider existing connections anymore for subsequent connection attempts so that the connection limit can be exceeded.
This issue affects Junos OS Evolved:

  *  All versions before 21.4R3-S4-EVO,
  *  22.1-EVO versions before 22.1R3-S3-EVO,
  *  22.2-EVO versions before 22.2R3-S2-EVO, 
  *  22.3-EVO versions before 22.3R2-S1-EVO, 22.3R3-EVO.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2024-30390 being exploited?

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

## Other vulnerabilities in Juniper Junos Os Evolved

- [CVE-2026-21902](https://insights.sbomify.com/CVE-2026-21902/): Junos OS Evolved: PTX Series: A vulnerability allows a unauthenticated, network-based attacker to execute code as root (critical 9.3)
- [CVE-2023-28983](https://insights.sbomify.com/CVE-2023-28983/): Junos OS Evolved: Shell Injection vulnerability in the gNOI server (high 8.8)
- [CVE-2025-21599](https://insights.sbomify.com/CVE-2025-21599/): Denial of service in Junos OS Evolved (high 8.7)
- [CVE-2024-47502](https://insights.sbomify.com/CVE-2024-47502/): Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS (high 8.7)
- [CVE-2024-39531](https://insights.sbomify.com/CVE-2024-39531/): Junos OS Evolved: ACX 7000 Series: Protocol specific DDoS configuration affects other protocols (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-30390 is a medium-severity denial of service vulnerability in Juniper Junos Os Evolved, 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-30390 in the wild and no public exploit code.

Affected product: Juniper Junos Os Evolved. 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-30390/ (Markdown: https://insights.sbomify.com/CVE-2024-30390/index.md)
```

## Sources

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

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