dbcve.org
JunosOperating system · Juniper

CVE-2018-0008

MEDIUM · 6.2 CVSS v3.0 Published 2018-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/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
An unauthenticated root login may allow upon reboot when a commit script is used. A commit script allows a device administrator to execute certain instructions during commit, which is configured under the [system scripts commit] stanza. Certain commit scripts that work without a problem during normal commit may cause unexpected behavior upon reboot which can leave the system in a state where root CLI login is allowed without a password due to the system reverting to a "safe mode" authentication state. Lastly, only logging in physically to the console port as root, with no password, will work. Affected releases are Juniper Networks Junos OS: 12.1X46 versions prior to 12.1X46-D71 on SRX; 12.3X48 versions prior to 12.3X48-D55 on SRX; 14.1 versions prior to 14.1R9; 14.1X53 versions prior to 14.1X53-D40 on QFX, EX; 14.2 versions prior to 14.2R7-S9, 14.2R8; 15.1 versions prior to 15.1F5-S7, 15.1F6-S8, 15.1R5-S6, 15.1R6; 15.1X49 versions prior to 15.1X49-D110 on SRX; 15.1X53 versions prior to 15.1X53-D232 on QFX5200/5110; 15.1X53 versions prior to 15.1X53-D49, 15.1X53-D470 on NFX; 15.1X53 versions prior to 15.1X53-D65 on QFX10K; 16.1 versions prior to 16.1R2. No other Juniper Networks products or platforms are affected by this issue.

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

Junos OS devices with commit scripts configured under [system scripts commit] can enter an unauthenticated 'safe mode' state upon reboot, allowing root console login without a password. This only affects physical console access and occurs when certain commit scripts cause unexpected behavior during the boot process. The vulnerability is triggered specifically upon device reboot, not during normal operation.

MitigationUpgrade to the fixed Junos OS versions specified in the advisory (12.1X46-D71, 12.3X48-D55, 14.1R9, 14.1X53-D40, 14.2R7-S9/14.2R8, 15.1F5-S7/15.1F6-S8/15.1R5-S6/15.1R6, 15.1X49-D110, 15.1X53-D232/D470/D65, 16.1R2 or later). Review and audit any commit scripts in use to ensure they do not trigger this behavior.

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.1x46= 12.3x48= 15.1x49= 14.1= 14.1x53= 14.2= 15.1= 15.1x53= 16.1

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
Physical
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Junos OS version
    Run 'show version' command to obtain the installed Junos OS version. Compare against the affected ranges: 12.1X46, 12.3X48, 15.1X49, 14.1, 14.1X53, 14.2, 15.1, 15.1X53, and 16.1 series.
    Affected if The installed version falls within any of these affected version families.
  2. Confirm commit scripts are configured
    Run 'show configuration system scripts commit' or view the config under [system scripts commit] hierarchy to determine if any commit scripts are active.
    Affected if Commit scripts are configured under [system scripts commit].
  3. Check for recent reboot events
    Review system logs and use 'show system reboot' to identify recent reboot events. The vulnerability is triggered specifically upon device reboot.
    Affected if The device has been rebooted since commit scripts were configured.
  4. Inspect console access configuration
    Run 'show configuration system ports' to check console settings. The vulnerability allows root console login without password on physical console access.
    Affected if Physical console access is enabled and the device is in or has entered an unauthenticated safe mode state.

A user is affected if they run an affected Junos version, have commit scripts configured under [system scripts commit], and the device has rebooted, allowing unauthenticated root console 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

Upgrade to the fixed Junos OS versions specified in the advisory (12.1X46-D71, 12.3X48-D55, 14.1R9, 14.1X53-D40, 14.2R7-S9/14.2R8, 15.1F5-S7/15.1F6-S8/15.1R5-S6/15.1R6, 15.1X49-D110, 15.1X53-D232/D470/D65, 16.1R2 or later). Review and audit any commit scripts in use to ensure they do not trigger this behavior.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0008 — 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-2018-0008 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