dbcve.org
JunosOperating system · Juniper

CVE-2020-1630

MEDIUM · 5.5 CVSS v3.1 Published 2020-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A privilege escalation vulnerability in Juniper Networks Junos OS devices configured with dual Routing Engines (RE), Virtual Chassis (VC) or high-availability cluster may allow a local authenticated low-privileged user with access to the shell to perform unauthorized configuration modification. This issue does not affect Junos OS device with single RE or stand-alone configuration. This issue affects Juniper Networks Junos OS 12.3 versions prior to 12.3R12-S14; 12.3X48 versions prior to 12.3X48-D86, 12.3X48-D90; 14.1X53 versions prior to 14.1X53-D51; 15.1 versions prior to 15.1R7-S6; 15.1X49 versions prior to 15.1X49-D181, 15.1X49-D190; 15.1X53 versions prior to 15.1X53-D592; 16.1 versions prior to 16.1R4-S13, 16.1R7-S6; 16.2 versions prior to 16.2R2-S10; 17.1 versions prior to 17.1R2-S11, 17.1R3-S1; 17.2 versions prior to 17.2R1-S9, 17.2R3-S3; 17.3 versions prior to 17.3R3-S6; 17.4 versions prior to 17.4R2-S6, 17.4R3; 18.1 versions prior to 18.1R3-S7; 18.2 versions prior to 18.2R2-S5, 18.2R3-S1; 18.2 versions prior to 18.2X75-D12, 18.2X75-D33, 18.2X75-D420, 18.2X75-D60, 18.2X75-D411; 18.3 versions prior to 18.3R1-S5, 18.3R2-S1, 18.3R3; 18.4 versions prior to 18.4R1-S4, 18.4R2-S1, 18.4R3; 19.1 versions prior to 19.1R1-S2, 19.1R2; 19.2 versions prior to 19.2R1-S1, 19.2R2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A local privilege escalation vulnerability in Juniper Networks Junos OS allows an authenticated low-privileged user with shell access on devices configured with dual Routing Engines (RE), Virtual Chassis (VC), or high-availability clusters to perform unauthorized configuration modifications. Single RE or stand-alone configurations are not affected.

MitigationApply the appropriate Junos OS software update for your version branch as specified in the Juniper advisory; for affected dual-RE/VC/HA configurations, ensure only trusted personnel have shell access and schedule a maintenance window for the upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:= 12.3= 12.3x48= 14.1x53= 15.1= 15.1x49= 15.1x53= 16.1= 16.2= 17.1= 17.2= 17.3= 17.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Junos OS version
    Run 'show version' command via CLI to display the installed Junos OS version
    Affected if The displayed version matches any of these ranges: 12.3, 12.3x48, 14.1x53, 15.1, 15.1x49, 15.1x53, 16.1, 16.2, 17.1, 17.2, 17.3, or 17.4
  2. Verify Routing Engine configuration
    Run 'show chassis routing-engine' command to display the status and count of Routing Engines in the device
    Affected if The output shows multiple Routing Engines (more than one RE present or listed as 'Master' and 'Backup')
  3. Check Virtual Chassis status
    Run 'show virtual-chassis' command to display Virtual Chassis member information and topology
    Affected if The output indicates multiple VC members or shows the device as part of a Virtual Chassis configuration
  4. Confirm high-availability cluster status
    Run 'show chassis cluster status' command to display chassis cluster redundancy group status
    Affected if The output shows active HA cluster configuration with redundancy groups and peer node detected
  5. Assess shell access exposure
    Run 'show system users' or review user account configuration via 'show configuration system login' to identify low-privileged accounts with shell access
    Affected if Any user account with 'set system login user <username> class <class>' where class is not 'super-user' or 'administrator' but has shell access (class like 'operator' or 'read-only' with shell)

The device is affected if it runs a vulnerable Junos version (12.3 through 17.4) AND is configured with dual Routing Engines, Virtual Chassis, or high-availability clusters AND allows low-privileged users shell access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate Junos OS software update for your version branch as specified in the Juniper advisory; for affected dual-RE/VC/HA configurations, ensure only trusted personnel have shell access and schedule a maintenance window for the upgrade.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1630 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-1630 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data