dbcve.org
JunosOperating system · Juniper

CVE-2018-0016

HIGH · 7.5 CVSS v3.0 Published 2018-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
Receipt of a specially crafted Connectionless Network Protocol (CLNP) datagram destined to an interface of a Junos OS device may result in a kernel crash or lead to remote code execution. Devices are only vulnerable to the specially crafted CLNP datagram if 'clns-routing' or ES-IS is explicitly configured. Devices with without CLNS enabled are not vulnerable to this issue. Devices with IS-IS configured on the interface are not vulnerable to this issue unless CLNS routing is also enabled. This issue only affects devices running Junos OS 15.1. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1F5-S3, 15.1F6-S8, 15.1F7, 15.1R5; 15.1X49 versions prior to 15.1X49-D60; 15.1X53 versions prior to 15.1X53-D66, 15.1X53-D233, 15.1X53-D471. Earlier releases are unaffected by this vulnerability, and the issue has been resolved in Junos OS 16.1R1 and all subsequent releases.

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 specially crafted CLNP (Connectionless Network Protocol) datagram can cause a kernel crash or remote code execution on Junos OS devices when CLNS routing or ES-IS is explicitly configured. Devices without CLNS enabled or with only IS-IS configured are not vulnerable. The vulnerability affects Junos OS 15.1 variants prior to specific patch levels and is fixed in 16.1R1 and later.

MitigationDisable CLNS routing and ES-IS if not required, or upgrade to Junos OS 16.1R1/higher or the specified patched versions (15.1F5-S3, 15.1X49-D60, 15.1X53-D66, etc.) to remediate this vulnerability.

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:= 15.1= 15.1f= 15.1f2= 15.1f3= 15.1f4= 15.1f5= 15.1f6= 15.1x49= 15.1x53

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

CVSS:3.0/AV:N/AC:H/PR:L/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. Check Junos OS version
    Run 'show version' or 'show version detail' to identify the installed Junos version
    Affected if Version matches any of these: 15.1, 15.1f, 15.1f2, 15.1f3, 15.1f4, 15.1f5, 15.1f6, 15.1x49, 15.1x53 (or any 15.1X49 or 15.1X53 variant)
  2. Verify CLNS routing configuration
    Run 'show configuration protocols clns' to see if CLNS routing is configured
    Affected if Output shows 'protocol clns' or any CLNS routing configuration under the [protocols] hierarchy
  3. Verify ES-IS configuration
    Run 'show configuration protocols esis' to see if ES-IS is configured
    Affected if Output shows 'protocol esis' configuration under the [protocols] hierarchy
  4. Confirm IS-IS only does not expose the vulnerability
    If only IS-IS is configured and no CLNS or ES-IS, the device is not vulnerable
    Affected if CLNS and ES-IS are both absent; only IS-IS is configured (this is NOT vulnerable)

Device is affected only if running an affected Junos 15.1 variant AND has either CLNS routing or ES-IS explicitly configured; if CLNS/ES-IS are not enabled, the vulnerability does not apply regardless of version.

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

Disable CLNS routing and ES-IS if not required, or upgrade to Junos OS 16.1R1/higher or the specified patched versions (15.1F5-S3, 15.1X49-D60, 15.1X53-D66, etc.) to remediate this vulnerability.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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