Security readout for executives and security teams
Plain-English summary
Affected Juniper Junos OS devices can lose availability when a permitted local user repeatedly runs a specific diagnostic CLI command. Each run leaks memory, eventually crashing daemons or the kernel and causing traffic loss. The supplied sources do not show active exploitation, but the impact matters for critical network devices.
Executive priority
Treat this as a moderate availability risk. It is not presented as remote or actively exploited, but affected network infrastructure can lose traffic if an authorized CLI user triggers the condition repeatedly.
Technical view
CVE-2021-0293 is a CWE-401 memory leak in Junos OS triggered by repeated use of the affected CLI behavior. Leak size depends on TCP connection volume. Over time, the netstat process, daemons, and ultimately the kernel can run out of memory, producing sustained DoS. CVSS is 5.5, local, low-privilege, availability-high.
Likely exposure
Exposure is limited to Juniper Networks Junos OS 18.2 through 20.3 releases listed as affected, before the fixed release trains named by Juniper. Junos OS before 18.2R1 is stated as not affected.
Exploitation context
The provided evidence describes local authenticated exploitation requiring CLI access and repeated command execution. CISA KEV status is false in the bundle, and no supplied source claims active exploitation in the wild.
Researcher notes
Key constraints are local access and repeat execution. Validation should focus on version exposure, administrator access paths, memory-growth telemetry, and kernel out-of-swap logs. The source bundle does not provide exploit prevalence or additional mitigations beyond fixed releases and monitoring indicators.
Mitigation direction
- Upgrade affected Junos OS devices to Juniper's fixed releases or later.
- Prioritize internet-edge and core routing devices where traffic loss has high business impact.
- Restrict CLI access to trusted administrators and review low-privilege operational roles.
- Monitor vendor guidance for platform-specific upgrade paths or compensating controls.
Validation and detection
- Inventory Junos OS versions and compare them with Juniper's affected and fixed release lists.
- Check whether devices run affected 18.2 through 20.3 release trains.
- Review logs for netstat out-of-memory or out-of-swap messages described by Juniper.
- Monitor memory consumption patterns on devices where remediation is pending.
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-401: 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-0293 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
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://kb.juniper.net/JSA11195CVE 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.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
