LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0239: Junos OS Evolved: Denial of Service due to receipt of specific genuine layer 2 frames.

In Juniper Networks Junos OS Evolved, receipt of a stream of specific genuine Layer 2 frames may cause the Advanced Forwarding Toolkit (AFT) manager process (Evo-aftmand), responsible for handling Route, Class-of-Service (CoS), Firewall operations within the packet forwarding engine (PFE) to crash and restart, leading to a Denial of Service (DoS) condition. By continuously sending this specific stream of genuine Layer 2 frames, an attacker can repeatedly crash the PFE, causing a sustained Denial of Service (DoS). This issue affects Juniper Networks Junos OS Evolved: All versions prior to 20.4R1-EVO. This issue does not affect Junos OS versions.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a denial-of-service flaw in Juniper Junos OS Evolved. Specific legitimate Layer 2 traffic can crash and restart a forwarding component, disrupting packet forwarding. The impact is availability only, but repeated traffic could sustain an outage on affected network devices.

Executive priority

Treat as a moderate operational risk for affected Juniper network infrastructure. Prioritize remediation where outages would affect customer traffic, data centers, or shared Layer 2 access networks. No confidentiality or integrity impact is described in the supplied sources.

Technical view

CVE-2021-0239 affects Junos OS Evolved before 20.4R1-EVO. A stream of specific genuine Layer 2 frames can crash Evo-aftmand, the AFT manager for route, CoS, and firewall operations in the PFE, causing repeated PFE disruption and DoS. Standard Junos OS is stated as unaffected.

Likely exposure

Exposure is limited to Juniper Networks devices running Junos OS Evolved versions earlier than 20.4R1-EVO. The CVSS vector indicates adjacent-network access is required, so risk is highest on shared or untrusted Layer 2 segments.

Exploitation context

The provided bundle does not show CISA KEV listing or other evidence of active exploitation. The attack condition is adjacent network reachability and repeated delivery of specific legitimate Layer 2 frames, resulting in availability impact rather than data compromise.

Researcher notes

The source bundle is specific but limited. It names the crashing process, affected product line, fixed threshold, and non-impact to Junos OS. It does not provide packet details, workarounds, exploit prevalence, or broader affected platform mapping.

Mitigation direction

  • Upgrade affected Junos OS Evolved systems to 20.4R1-EVO or later.
  • Review Juniper advisory JSA11134 for exact fixed-release and operational guidance.
  • Prioritize edge, shared-access, and untrusted Layer 2 environments.
  • Confirm standard Junos OS systems are not incorrectly included in remediation scope.

Validation and detection

  • Inventory Juniper devices running Junos OS Evolved and record versions.
  • Identify systems below 20.4R1-EVO as affected.
  • Check device logs for Evo-aftmand crashes, restarts, or PFE instability.
  • Map affected interfaces connected to adjacent or shared Layer 2 networks.
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-0239 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-0239Attack 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 OS EvolvedunspecifiedListed
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.