# CVE-2022-22210: Junos OS: QFX5000 Series and MX Series: An l2alm crash leading to an FPC crash can be observed in VxLAN scenario

> An unauthenticated adjacent attacker can cause a sustained denial of service on Juniper QFX5000 and MX series devices by sending specific VxLAN packets.

- **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:** 20 Jul 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-468h-vwvc-rxx5

## What is CVE-2022-22210?

CVE-2022-22210 is a medium-severity vulnerability in Juniper Junos, published on 20 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A NULL Pointer Dereference vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on QFX5000 Series and MX Series allows an unauthenticated adjacent attacker to cause a Denial of Service (DoS). On QFX5K Series and MX Series, when the PFE receives a specific VxLAN packet the Layer 2 Address Learning Manager (L2ALM) process will crash leading to an FPC reboot. Continued receipt of this specific packet will create a sustained Denial of Service (DoS) condition. This issue affects Juniper Networks Junos OS on QFX5000 Series, MX Series: 20.3 versions prior to 20.3R3-S3; 20.4 versions prior to 20.4R3-S2; 21.2 versions prior to 21.2R2-S1. This issue does not affect Juniper Networks Junos OS: All versions prior to 20.3R1; 21.1 version 21.1R1 and later versions.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2022-22210 being exploited?

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

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

## Sources

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

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