# CVE-2023-28965: Junos OS: QFX10002: Failure of storm control feature may lead to Denial of Service

> An attacker can cause a sustained Denial of Service on Juniper QFX10002 switches by sending high-rate traffic that bypasses storm control protections.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2023
- **Updated:** 6 Feb 2025
- **Also known as:** GHSA-gp64-4ccq-3vpw

## What is CVE-2023-28965?

CVE-2023-28965 is a medium-severity denial of service vulnerability in Juniper Junos, published on 17 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Improper Check or Handling of Exceptional Conditions within the storm control feature of Juniper Networks Junos OS allows an attacker sending a high rate of traffic to cause a Denial of Service. Continued receipt and processing of these packets will create a sustained Denial of Service (DoS) condition. Storm control monitors the level of applicable incoming traffic and compares it with the level specified. If the combined level of the applicable traffic exceeds the specified level, the switch drops packets for the controlled traffic types. This issue affects Juniper Networks Junos OS on QFX10002: All versions prior to 19.3R3-S7; 19.4 versions prior to 19.4R3-S11; 20.2 versions prior to 20.2R3-S6; 20.4 versions prior to 20.4R3-S5; 21.1 versions prior to 21.1R3-S4; 21.2 versions prior to 21.2R3-S3; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R2.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions), CWE-703 (Improper Check or Handling of Exceptional Conditions)

## Which versions are affected by CVE-2023-28965?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2023-28965?

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

## Is CVE-2023-28965 being exploited?

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

What it is: CVE-2023-28965 is a medium-severity denial of service vulnerability in Juniper Junos, published on 17 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-28965 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-2023-28965/ (Markdown: https://insights.sbomify.com/CVE-2023-28965/index.md)
```

## Sources

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

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