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-22168Junos OS: vMX and MX150: Specific packets might cause a memory leak and eventually an FPC reboot

Description

An Improper Validation of Specified Type of Input vulnerability in the kernel of Juniper Networks Junos OS allows an unauthenticated adjacent attacker to trigger a Missing Release of Memory after Effective Lifetime vulnerability. Continued exploitation of this vulnerability will eventually lead to an FPC reboot and thereby a Denial of Service (DoS). This issue affects: Juniper Networks Junos OS on vMX and MX150: All versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S5; 19.4 versions prior to 19.4R2-S5, 19.4R3-S6; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2-S1, 21.1R3; 21.2 versions prior to 21.2R1-S1, 21.2R2; 21.3 versions prior to 21.3R1-S1, 21.3R2.

Timeline

  1. ID reserved

    By juniper

  2. · 29 days later

    Published

  3. · 3 years later

    Record updated

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-22168, by who scored it
Scored byCVSSScoreVector
juniperCNA (assigner)3.1Medium6.5CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium6.5CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.40% · top 65% of all CVEs (18 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Juniper Networks · Junos OS

    • affected unspecified – < 19.2R1-S8, 19.2R3-S4
    • affected 19.3 – < 19.3R3-S5
    • affected 19.4 – < 19.4R2-S5, 19.4R3-S6
    • affected 20.1 – < 20.1R3-S2
    • affected 20.2 – < 20.2R3-S3
    • affected 20.3 – < 20.3R3-S1
    • affected 20.4 – < 20.4R3
    • affected 21.1 – < 21.1R2-S1, 21.1R3
    • affected 21.2 – < 21.2R1-S1, 21.2R2
    • affected 21.3 – < 21.3R1-S1, 21.3R2

What to do

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

Workaround: There is no viable workaround 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-22168 badge
[![CVE-2022-22168](https://cveledger.app/badge/CVE-2022-22168.svg)](https://cveledger.app/cve/CVE-2022-22168)

Record last updated .