LiveActive security incident?Get immediate response
CVE Record

CVE-2020-1618: Junos OS: EX and QFX Series: Console port authentication bypass vulnerability

On Juniper Networks EX and QFX Series, an authentication bypass vulnerability may allow a user connected to the console port to login as root without any password. This issue might only occur in certain scenarios: • At the first reboot after performing device factory reset using the command “request system zeroize”; or • A temporary moment during the first reboot after the software upgrade when the device configured in Virtual Chassis mode. This issue affects Juniper Networks Junos OS on EX and QFX Series: 14.1X53 versions prior to 14.1X53-D53; 15.1 versions prior to 15.1R7-S4; 15.1X53 versions prior to 15.1X53-D593; 16.1 versions prior to 16.1R7-S4; 17.1 versions prior to 17.1R2-S11, 17.1R3-S1; 17.2 versions prior to 17.2R3-S3; 17.3 versions prior to 17.3R2-S5, 17.3R3-S6; 17.4 versions prior to 17.4R2-S9, 17.4R3; 18.1 versions prior to 18.1R3-S8; 18.2 versions prior to 18.2R2; 18.3 versions prior to 18.3R1-S7, 18.3R2. This issue does not affect Juniper Networks Junos OS 12.3.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Certain Juniper EX and QFX switches could briefly allow root login from the physical console without a password. The risk is mainly during the first reboot after factory reset, or briefly after software upgrade in Virtual Chassis mode. This is serious for sites where console access is not tightly controlled.

Executive priority

Prioritize remediation for switches in shared, remote, or contractor-accessible environments. Internet exposure is not the main issue; physical console control is. Schedule upgrades through normal network maintenance, and tighten console access until all affected devices are remediated.

Technical view

CVE-2020-1618 is a CWE-288 authentication bypass in Junos OS on EX and QFX Series. Affected releases before listed fixed versions may allow unauthenticated root console access during narrow reboot scenarios. CVSS 3.1 is 6.3, with physical access and high complexity but high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on Juniper EX or QFX devices running affected Junos OS versions, especially during zeroize recovery or Virtual Chassis upgrades. Devices with accessible console ports, shared facilities, or weak physical controls face higher practical risk. Junos OS 12.3 is stated as unaffected.

Exploitation context

The source bundle does not show KEV listing or active exploitation. Practical exploitation requires physical console access and timing around specific first-reboot conditions, limiting broad internet-scale risk while leaving meaningful insider, contractor, or data-center physical-access risk.

Researcher notes

The vulnerability is constrained but high impact when reachable: unauthenticated root via console during specific boot states. Evidence in the bundle does not support active exploitation claims. Validate exposure by version, platform, reboot scenario, and physical access path rather than by network scanning alone.

Mitigation direction

  • Upgrade affected EX/QFX devices to the fixed Junos OS releases listed by Juniper.
  • Restrict physical access to console ports and out-of-band management areas.
  • Treat zeroize and Virtual Chassis upgrade reboots as controlled maintenance events.
  • Review Juniper JSA11001 for current vendor guidance before remediation.
  • Document compensating controls where immediate upgrade is not possible.

Validation and detection

  • Inventory Juniper EX and QFX devices and record Junos OS versions.
  • Compare versions against the affected and fixed ranges in JSA11001.
  • Identify devices configured in Virtual Chassis mode.
  • Review recent zeroize and software upgrade maintenance records.
  • Confirm console ports are physically secured and access is logged.
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-288: 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
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-1618 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/I:H/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.3CVSS 3.1MediumCVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H0.45.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2020-1618Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/I:H/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 OS12.3, 14.1X53, 15.1, 15.1X53, 16.1, 17.1, 17.2, 17.3, 17.4, 18.1, 18.2, 18.3Listed
Weakness

CWE details

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

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.