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-2021-0222Junos OS: Upon receipt of certain protocol packets with invalid payloads a self-propagating Denial of Service may occur.

Description

A vulnerability in Juniper Networks Junos OS allows an attacker to cause a Denial of Service (DoS) to the device by sending certain crafted protocol packets from an adjacent device with invalid payloads to the device. These crafted packets, which should be discarded, are instead replicated and sent to the RE. Over time, a Denial of Service (DoS) occurs. Continued receipt of these crafted protocol packets will cause an extended Denial of Service (DoS) condition, which may cause wider traffic impact due to protocol flapping. An indication of compromise is to check "monitor interface traffic" on the ingress and egress port packet counts. For each ingress packet, two duplicate packets are seen on egress. This issue can be triggered by IPv4 and IPv6 packets. This issue affects all traffic through the device. This issue affects: Juniper Networks Junos OS: 14.1X53 versions prior to 14.1X53-D53 on EX4300, QFX3500, QFX5100, EX4600; 15.1 versions prior to 15.1R7-S6 on EX4300, QFX3500, QFX5100, EX4600; 16.1 versions prior to 16.1R7-S7 on EX4300, QFX5100, EX4600; 17.1 versions prior to 17.1R2-S11 on EX4300, QFX5100, EX4600; 17.1 versions prior to 117.1R3-S2 on EX4300; 17.2 versions prior to 17.2R1-S9 on EX4300; 17.2 versions prior to 17.2R3-S3 on EX4300, QFX5100, EX4600, QFX5110, QFX5200; 17.3 versions prior to 17.3R2-S5, 17.3R3-S7 on EX4300, QFX5100, EX4600, QFX5110, QFX5200; 17.4 versions prior to 17.4R2-S9, 17.4R3 on EX4300, QFX5100, EX4600, QFX5110, QFX5200; 18.1 versions prior to 18.1R3-S9 on EX4300, QFX5100, EX4600, QFX5110, QFX5200, QFX5210, EX2300, EX3400; 18.2 versions prior to 18.2R2-S7 on EX4300; 18.2 versions prior to 18.2R3-S3 on EX4300, QFX5100, EX4600, QFX5110, QFX5200, QFX5210, EX2300, EX3400; 18.3 versions prior to 18.3R2-S3, on EX4300; 18.3 versions prior to 18.3R1-S7, 18.3R3-S1 on EX4300, QFX5100, EX4600, QFX5110, QFX5200, QFX5210, QFX5120, EX4650, EX2300, EX3400; 18.4 versions prior to 18.4R1-S5, 18.4R2-S3, 18.4R3 on EX4300, QFX5100, EX4600, QFX5110, QFX5200, QFX5210, QFX5120, EX4650, EX2300, EX3400; 19.1 versions prior to 19.1R1-S4, 19.1R2-S1, 19.1R3 on EX4300, QFX5100, EX4600, QFX5110, QFX5200, QFX5210, QFX5120, EX4650, EX2300, EX3400; 19.2 versions prior to 19.2R1-S4, 19.2R2 on EX4300; 19.2 versions prior to 19.2R1-S3, 19.2R2 on QFX5100, EX4600, QFX5110, QFX5200, QFX5210, QFX5120, EX4650, EX2300, EX3400; 19.3 versions prior to 19.3R2-S1, 19.3R3 on EX4300; 19.3 versions prior to 19.3R1-S1, 19.3R2, 19.3R3 on QFX5100, EX4600, QFX5110, QFX5200, QFX5210, QFX5120, EX4650, EX2300, EX3400;

Timeline

  1. ID reserved

    By juniper

  2. · 3 months later

    Published

  3. · 4 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-2021-0222, by who scored it
Scored byCVSSScoreVector
juniperCNA (assigner)3.1High7.4CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
NVDNVD · Modified3.1High7.4CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.65% · top 48% of all CVEs (16 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.4.

Affected products

  • Juniper Networks · Junos OS

    • affected 14.1X53 – < 14.1X53-D53
    • affected 15.1 – < 15.1R7-S6
  • Juniper Networks · Junos OS

    • affected 16.1 – < 16.1R7-S7
    • affected 17.1 – < 17.1R2-S11
  • Juniper Networks · Junos OS

    • affected 17.1 – < 17.1R3-S2
    • affected 17.2 – < 17.2R1-S9
    • affected 18.2 – < 18.2R2-S7
    • affected 18.3 – < 18.3R2-S3
    • affected 19.2 – < 19.2R1-S3, 19.2R2
    • affected 19.3 – < 19.3R2-S1, 19.3R3
  • Juniper Networks · Junos OS

    • affected 17.2 – < 17.2R3-S3
    • affected 17.3 – < 17.3R2-S5, 17.3R3-S7
    • affected 17.4 – < 17.4R2-S9, 17.4R3
  • Juniper Networks · Junos OS

    • affected 18.1 – < 18.1R3-S9
    • affected 18.2 – < 18.2R3-S3
  • Juniper Networks · Junos OS

    • affected 18.3 – < 18.3R1-S7, 18.3R3-S1
    • affected 18.4 – < 18.4R1-S5, 18.4R2-S3, 18.4R3
    • affected 19.1 – < 19.1R1-S4, 19.1R2-S1, 19.1R3
  • Juniper Networks · Junos OS

    • affected 19.2 – < 19.2R1-S4, 19.2R2
    • affected 19.3 – < 19.3R1-S1, 19.3R2, 19.3R3

What to do

Solution: The following software releases have been updated to resolve this specific issue: 14.1X53-D53, 15.1R7-S6, 16.1R7-S7, 17.1R2-S11, 17.2R3-S3, 17.3R2-S5, 17.3R3-S7, 17.4R2-S9, 17.4R3, 18.1R3-S9, 18.2R3-S3, 18.4R1-S5, 18.4R2-S3, 18.4R3, 19.1R1-S4, 19.1R2-S1, 19.1R3, 19.2R2, 19.3R2-S1, 19.3R3, 19.4R1, and all subsequent releases.

Workaround: There are no available workarounds for this issue.

References

References1

Sources

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

Badge for a README or a ticket

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

Record last updated .