# CVE-2022-22183: Denial of service in Junos OS

> Remote attackers can cause a CPU denial of service on Junos OS Evolved devices by sending traffic to a specific open IPv4 port.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p879-gfvw-mvjh

## What is CVE-2022-22183?

CVE-2022-22183 is a high-severity denial of service vulnerability in Juniper Junos Os Evolved, published on 14 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Improper Access Control vulnerability in Juniper Networks Junos OS Evolved allows a network-based unauthenticated attacker who is able to connect to a specific open IPv4 port, which in affected releases should otherwise be unreachable, to cause the CPU to consume all resources as more traffic is sent to the port to create a Denial of Service (DoS) condition. Continued receipt and processing of these packets will create a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS Evolved 20.4 versions prior to 20.4R3-S2-EVO; 21.1 versions prior to 21.1R3-S1-EVO; 21.2 versions prior to 21.2R3-EVO; 21.3 versions prior to 21.3R2-EVO; 21.4 versions prior to 21.4R2-EVO. This issue does not affect Junos OS.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-16

## Which versions are affected by CVE-2022-22183?

It affects 1 product.


Products: Juniper Junos Os Evolved.

## How do I fix CVE-2022-22183?

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

## Is CVE-2022-22183 being exploited?

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

What it is: CVE-2022-22183 is a high-severity denial of service vulnerability in Juniper Junos Os Evolved, published on 14 Apr 2022. 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-2022-22183 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-2022-22183/ (Markdown: https://insights.sbomify.com/CVE-2022-22183/index.md)
```

## Sources

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

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