Security readout for executives and security teams
Plain-English summary
Certain Juniper core and data-center routing platforms may not apply custom DDoS protection settings as intended. Under a high rate of specific packets, BFD sessions can flap, which can disrupt routing stability and create a denial-of-service condition.
Executive priority
Prioritize remediation on backbone, edge, and data-center fabrics where BFD instability could cause customer-visible outages or route churn. This is not a data theft issue, but it can affect service availability on critical network infrastructure.
Technical view
CVE-2021-0280 is an improper initialization flaw in Junos OS PFE DDoS policer handling on PTX and QFX10K/QFX10002 platforms using Paradise chipset line cards. CLI ddos-protection changes may not take effect beyond defaults, allowing specific high-rate packet traffic to trigger BFD flaps and availability impact.
Likely exposure
Exposure is limited to listed Juniper PTX and QFX10K/QFX10002 platforms with Paradise chipset-based line cards running affected Junos OS releases 17.4 through 20.4 before the fixed versions. Environments relying on BFD for routing convergence face higher operational risk.
Exploitation context
The provided sources do not state active exploitation, and KEV is false. The vulnerability is network-reachable, unauthenticated, low complexity, and availability-only. Impact depends on sustained receipt of high-rate specific packets causing BFD instability.
Researcher notes
The key behavior is failed application of non-default PFE DDoS policer configuration after CLI changes. Validate exposure through asset/version/chipset matching rather than generic Junos presence. Sources do not provide packet details, proof-of-concept status, or workaround specifics beyond fixed releases.
Mitigation direction
- Upgrade affected Junos OS releases to the fixed versions listed by Juniper or later.
- Confirm platform and line-card chipset before treating a device as affected.
- Review Juniper JSA11184 for vendor-specific remediation guidance.
- Monitor BFD session stability and routing adjacency changes until remediation completes.
- Do not rely on custom ddos-protection CLI changes as a complete mitigation.
Validation and detection
- Inventory PTX and QFX10K/QFX10002 devices and installed Junos OS versions.
- Identify Paradise chipset-based line cards in affected platforms.
- Compare running releases against Juniper's fixed-version list.
- Review BFD flap logs and routing protocol instability around high packet-rate events.
- Verify upgraded devices retain expected routing and BFD stability.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-665: 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 lookupCVE-2021-0280 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://kb.juniper.net/JSA11184CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Initialization
Improper Initialization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
