Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-22161Junos OS: MX104 might become unresponsive if the out-of-band management port receives a flood of traffic

Description

An Uncontrolled Resource Consumption vulnerability in the kernel of Juniper Networks Junos OS allows an unauthenticated network based attacker to cause 100% CPU load and the device to become unresponsive by sending a flood of traffic to the out-of-band management ethernet port. Continued receipted of a flood will create a sustained Denial of Service (DoS) condition. Once the flood subsides the system will recover by itself. An indication that the system is affected by this issue would be that an irq handled by the fman process is shown to be using a high percentage of CPU cycles like in the following example output: user@host> show system processes extensive ... PID USERNAME PRI NICE SIZE RES STATE TIME WCPU COMMAND 31 root -84 -187 0K 16K WAIT 22.2H 56939.26% irq96: fman0 This issue affects Juniper Networks Junos OS: All versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S9; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S7, 19.2R3-S3; 19.3 versions prior to 19.3R2-S7, 19.3R3-S4; 19.4 versions prior to 19.4R2-S5, 19.4R3-S5; 20.1 versions prior to 20.1R3-S1; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R2-S2, 20.4R3; 21.1 versions prior to 21.1R2; 21.2 versions prior to 21.2R1-S1, 21.2R2.

Timeline

  1. ID reserved

    By juniper

  2. · 29 days later

    Published

  3. · 3 years later

    Record updated

  4. · 2 years later

    EPSS rose above 1%

    0.97% → 1.0%

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-22161, by who scored it
Scored byCVSSScoreVector
juniperCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
1.0% · top 37% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Juniper Networks · Junos OS

    • affected unspecified – < 18.3R3-S6
    • affected 18.4 – < 18.4R2-S9, 18.4R3-S9
    • affected 19.1 – < 19.1R2-S3, 19.1R3-S7
    • affected 19.2 – < 19.2R1-S7, 19.2R3-S3
    • affected 19.3 – < 19.3R2-S7, 19.3R3-S4
    • affected 19.4 – < 19.4R2-S5, 19.4R3-S5
    • affected 20.1 – < 20.1R3-S1
    • affected 20.2 – < 20.2R3-S2
    • affected 20.3 – < 20.3R3-S1
    • affected 20.4 – < 20.4R2-S2, 20.4R3
    • affected 21.1 – < 21.1R2
    • affected 21.2 – < 21.2R1-S1, 21.2R2

What to do

Solution: The following software releases have been updated to resolve this specific issue: 18.3R3-S6, 18.4R2-S9, 18.4R3-S9, 19.1R2-S3, 19.1R3-S7, 19.2R1-S7, 19.2R3-S3, 19.3R2-S7, 19.3R3-S4, 19.4R2-S5, 19.4R3-S5, 20.1R3-S1, 20.2R3-S2, 20.3R3-S1, 20.4R2-S2, 20.4R3, 21.1R2, 21.2R1-S1, 21.2R2, 21.3R1, and all subsequent releases.

Workaround: There are no viable workarounds for this issue.

Exploitation: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-22161 badge
[![CVE-2022-22161](https://cveledger.app/badge/CVE-2022-22161.svg)](https://cveledger.app/cve/CVE-2022-22161)

Record last updated .