LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0287: Junos OS and Junos OS Evolved: RPD could crash in SR-ISIS/MPLS environment due to a flap of an ISIS link in the network

In a Segment Routing ISIS (SR-ISIS)/MPLS environment, on Juniper Networks Junos OS and Junos OS Evolved devices, configured with ISIS Flexible Algorithm for Segment Routing and sensor-based statistics, a flap of a ISIS link in the network, can lead to a routing process daemon (RPD) crash and restart, causing a Denial of Service (DoS). Continued link flaps will create a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS: 19.4 versions prior to 19.4R1-S4, 19.4R3-S2; 20.1 versions prior to 20.1R2-S1, 20.1R3; 20.2 versions prior to 20.2R2-S2, 20.2R3; 20.3 versions prior to 20.3R2; Juniper Networks Junos OS Evolved: 20.3-EVO versions prior to 20.3R2-EVO; 20.4-EVO versions prior to 20.4R2-EVO. This issue does not affect: Juniper Networks Junos OS releases prior to 19.4R1. Juniper Networks Junos OS Evolved releases prior to 19.4R1-EVO.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability can make affected Juniper routing devices restart their routing process when a specific SR-ISIS/MPLS setup experiences ISIS link flapping. The business impact is availability: routing disruption or sustained denial of service if link instability continues. It is not described as data theft or unauthorized access.

Executive priority

Treat this as a targeted availability risk for critical routing infrastructure. Prioritize remediation on backbone or service-impacting Juniper devices that match the affected configuration, especially where routing process restarts would disrupt customer or internal connectivity.

Technical view

CVE-2021-0287 affects Junos OS and Junos OS Evolved in SR-ISIS/MPLS environments using ISIS Flexible Algorithm for Segment Routing and sensor-based statistics. An ISIS link flap can crash and restart RPD. Continued flaps can sustain denial of service. CVSS 3.1 is 6.5 with high availability impact.

Likely exposure

Exposure is likely limited to Juniper networks running affected Junos OS or Junos OS Evolved releases with SR-ISIS/MPLS, ISIS Flexible Algorithm, and sensor-based statistics enabled. This is most relevant to service provider, backbone, and advanced enterprise routing environments, not typical edge-only deployments.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The triggering condition is an ISIS link flap in the affected network configuration. Repeated flaps can prolong denial of service, but no public exploit activity is cited in the provided sources.

Researcher notes

CVSS indicates adjacent attack vector, low complexity, no privileges, no user interaction, and high availability impact. Affected versions include specific 19.4, 20.1, 20.2, 20.3, and EVO 20.3/20.4 trains. The sources do not provide exploit details or workaround confirmation beyond fixed releases.

Mitigation direction

  • Upgrade affected Junos OS releases to the fixed versions identified by Juniper.
  • Upgrade affected Junos OS Evolved releases to the fixed EVO versions identified by Juniper.
  • Prioritize devices using SR-ISIS/MPLS with ISIS Flexible Algorithm and sensor-based statistics.
  • Review Juniper advisory JSA11189 before choosing an upgrade path.
  • Monitor and investigate repeated ISIS link flaps until remediation is complete.

Validation and detection

  • Inventory Juniper devices and record Junos OS or Junos OS Evolved versions.
  • Confirm whether SR-ISIS/MPLS, ISIS Flexible Algorithm, and sensor-based statistics are enabled.
  • Check operational logs for RPD crashes or restarts near ISIS link flaps.
  • Verify upgraded devices run a non-affected release from the advisory.
  • Track recurrence of ISIS flaps and RPD restarts after remediation.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-754: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-0287 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-0287Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OSunspecified, 19.4R1, 20.1, 20.2, 20.3Listed
Juniper NetworksJunos OS Evolvedunspecified, 19.4R1-EVO, 20.1R1-EVO, 20.2R1-EVO, 20.3, 20.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-754 · source CWE mapping

Improper Check for Unusual or Exceptional Conditions

Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.