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

> An unauthenticated attacker can crash the routing daemon by sending a malformed BGP update when update tracing is enabled, causing a denial of service.

- **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:** 19 Jan 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fgwx-697g-22hm

## What is CVE-2022-22166?

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

### Official description

An Improper Validation of Specified Quantity in Input vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS allows an unauthenticated networked attacker to cause an rdp crash and thereby a Denial of Service (DoS). If a BGP update message is received over an established BGP session where a BGP SR-TE policy tunnel attribute is malformed and BGP update tracing flag is enabled, the rpd will core. This issue can happen with any BGP session as long as the previous conditions are met. This issue can not propagate as the crash occurs as soon as the malformed update is received. This issue affects Juniper Networks Junos OS: 20.4 versions prior to 20.4R3-S1; 21.1 versions prior to 21.1R2-S2, 21.1R3. This issue does not affect Juniper Networks Junos OS versions prior to 20.4R1.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2022-22166 being exploited?

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

What it is: CVE-2022-22166 is a medium-severity denial of service vulnerability in Juniper Junos, published on 19 Jan 2022. 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-2022-22166 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-2022-22166/ (Markdown: https://insights.sbomify.com/CVE-2022-22166/index.md)
```

## Sources

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

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