Security readout for executives and security teams
Plain-English summary
This is a network-facing denial-of-service flaw in Juniper routing software. In SRTE deployments with BMP enabled, a crafted BGP update can crash the routing protocol daemon. Repeated messages can keep routing services down, disrupting network availability rather than exposing data.
Executive priority
Prioritize remediation for affected Juniper routers that support critical routing paths or external BGP adjacency. The issue is availability-focused but can create sustained routing disruption if vulnerable devices repeatedly process the triggering update.
Technical view
CVE-2021-0250 affects RPD in Junos OS and Junos OS Evolved when Segment Routing Traffic Engineering and BGP Monitoring Protocol are in use. The CVSS 3.1 vector shows unauthenticated network-triggered availability impact across IPv4 and IPv6.
Likely exposure
Exposure is limited to Juniper Junos OS 17.4R1 and later through specified unfixed 19.2 trains, and Junos OS Evolved 19.2-EVO before 19.2R2-EVO, in SRTE environments with BMP enabled. Releases before 17.4R1 are stated as unaffected.
Exploitation context
The provided sources describe a specific crafted BGP update message causing RPD to core. They do not identify public exploit code, exploitation in the wild, or CISA KEV listing. Treat peer-reachable BGP control planes as higher urgency.
Researcher notes
The source bundle is specific about feature prerequisites, affected trains, and fixed version thresholds. It does not include exploit telemetry, proof-of-concept status, or detailed packet conditions. Validation should focus on feature exposure, version state, and RPD stability indicators.
Mitigation direction
- Upgrade Junos OS to a fixed release listed in Juniper advisory JSA11143.
- Upgrade Junos OS Evolved 19.2-EVO systems to 19.2R2-EVO or later.
- Confirm whether BMP is enabled in SRTE environments and prioritize those devices.
- Check Juniper guidance for any deployment-specific workarounds or operational constraints.
Validation and detection
- Inventory Junos OS and Junos OS Evolved versions against the affected release ranges.
- Identify routers using Segment Routing Traffic Engineering with BMP enabled.
- Review RPD crash logs or core files for unexplained routing daemon failures.
- Verify fixed software versions after maintenance windows complete.
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.
CVE-2021-0250 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/JSA11143CVE reference · x_refsource_MISC
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.
