dbcve.org
JunosOperating system · Juniper

CVE-2018-0037

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Junos OS routing protocol daemon (RPD) process may crash and restart or may lead to remote code execution while processing specific BGP NOTIFICATION messages. By continuously sending crafted BGP NOTIFICATION messages, an attacker can repeatedly crash the RPD process causing a sustained Denial of Service. Due to design improvements, this issue does not affect Junos OS 16.1R1, and all subsequent releases. This issue only affects the receiving BGP device and is non-transitive in nature. Affected releases are Juniper Networks Junos OS: 15.1F5 versions starting from 15.1F5-S7 and all subsequent releases; 15.1F6 versions starting from 15.1F6-S3 and later releases prior to 15.1F6-S10; 15.1F7 versions 15.1 versions starting from 15.1R5 and later releases, including the Service Releases based on 15.1R5 and on 15.1R6 prior to 15.1R6-S6 and 15.1R7;

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 vulnerability in the Junos OS routing protocol daemon (RPD) allows attackers to send crafted BGP NOTIFICATION messages that cause the RPD process to crash (Denial of Service) or potentially execute remote code. The attack is non-transitive, affecting only the receiving BGP device, and can be repeated to create a sustained DoS condition.

MitigationUpgrade to Junos OS 16.1R1 or later, or apply the specific Service Releases mentioned (15.1F6-S10+, 15.1R6-S6+, 15.1R7+). Alternatively, implement BGP peering controls and monitor for abnormal NOTIFICATION messages as interim measures.

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

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

CVSS:3.0/AV:N/AC:L/PR:N/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' on the Junos device to obtain the installed OS version.
    Affected if The installed version is exactly 15.1 (versions 15.1F6-S10+, 15.1R6-S6+, 15.1R7+ contain the fix).
  2. Verify BGP is configured
    Run 'show bgp summary' or 'show configuration protocols bgp' to determine if BGP is enabled and has configured peers.
    Affected if BGP is actively configured and has peering relationships, as the vulnerability is triggered by receiving crafted BGP NOTIFICATION messages.
  3. Inspect RPD crash history
    Run 'show system processes rpd' or review system logs with 'show log messages | match rpd' to check for recent RPD process crashes or unexpected restarts.
    Affected if RPD has crashed or restarted recently without an identified cause, which may indicate exploitation of this vulnerability.

A device is affected if it runs Junos OS version 15.1, has BGP configured with active peers, and is experiencing unexplained RPD crashes or BGP session resets triggered by incoming NOTIFICATION messages.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Junos OS 16.1R1 or later, or apply the specific Service Releases mentioned (15.1F6-S10+, 15.1R6-S6+, 15.1R7+). Alternatively, implement BGP peering controls and monitor for abnormal NOTIFICATION messages as interim measures.

Recommended fix High confidence

Upgrade to Junos OS 16.1R1 or any subsequent release (16.1R2, 16.1R3, etc.)

  1. Identify current Junos OS version using 'show version' command
  2. Determine if version is affected: 15.1F5-S7 through 15.1F5-x, 15.1F6-S3 through 15.1F6-S9, 15.1R5 through 15.1R6-S5, or any 15.1R7
  3. Schedule maintenance window for upgrade procedure
  4. Back up current configuration using 'request system configuration backup'
  5. Download Junos OS 16.1R1 or later from Juniper Networks support portal
  6. Upgrade the device using 'request system software add <package> reboot'
  7. Verify successful upgrade and RPD process stability using 'show chassis routing-engine'
  8. Confirm BGP peer stability using 'show bgp summary'
Caveat Upgrading between major Junos releases may introduce behavioral changes; review release notes for BGP, routing, and feature modifications before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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