dbcve.org
JunosOperating system · Juniper

CVE-2018-0030

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
Receipt of a specific MPLS packet may cause MPC7/8/9, PTX-FPC3 (FPC-P1, FPC-P2) line cards or PTX1K to crash and restart. By continuously sending specific MPLS packets, an attacker can repeatedly crash the line cards or PTX1K causing a sustained Denial of Service. Affected releases are Juniper Networks Junos OS with MPC7/8/9 or PTX-FPC3 (FPC-P1, FPC-P2) installed and PTX1K: 15.1F versions prior to 15.1F6-S10; 15.1 versions prior to 15.1R4-S9, 15.1R6-S6, 15.1R7; 16.1 versions prior to 16.1R3-S8, 16.1R4-S9, 16.1R5-S4, 16.1R6-S3, 16.1R7; 16.1X65 versions prior to 16.1X65-D46; 16.2 versions prior to 16.2R1-S6, 16.2R2-S5, 16.2R3; 17.1 versions prior to 17.1R1-S7, 17.1R2-S7, 17.1R3; 17.2 versions prior to 17.2R1-S4, 17.2R2-S4, 17.2R3; 17.2X75 versions prior to 17.2X75-D70, 17.2X75-D90; 17.3 versions prior to 17.3R1-S4, 17.3R2, 17.4 versions prior to 17.4R1-S2, 17.4R2. Refer to KB25385 for more information about PFE line cards.

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 denial of service vulnerability in Juniper Junos OS allows remote attackers to crash and restart MPC7/8/9, PTX-FPC3 (FPC-P1, FPC-P2) line cards or PTX1K platforms by sending specially crafted MPLS packets. Repeated exploitation causes sustained DoS.

MitigationApply the vendor-supplied Junos OS patches to the specified versions (15.1F6-S10, 15.1R7, 16.1R7, 17.4R2 or later) for affected releases. If patching is not immediately possible, consider filtering or rate-limiting MPLS traffic as a temporary workaround.

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= 16.1= 16.1x65= 16.2= 17.1= 17.2= 17.3= 17.4= 17.2x75

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify Junos OS version
    Run 'show version' or 'show version detail' on the device CLI to obtain the installed Junos OS version
    Affected if The version matches 15.1, 16.1, 16.1x65, 16.2, 17.1, 17.2, 17.3, 17.4, or 17.2x75 (any build within these release trains)
  2. Confirm MPLS protocol is enabled
    Run 'show configuration protocols mpls' or 'show configuration protocols' and search for 'mpls' statements to verify MPLS is configured
    Affected if MPLS protocol is actively configured on the device (the vulnerability is triggered by specially crafted MPLS packets)
  3. Identify line card hardware
    Run 'show chassis hardware' or 'show chassis fpc detail' to list installed Flexible PIC Concentrators (FPC) and MPC modules
    Affected if The device contains MPC7, MPC8, or MPC9 line cards, PTX-FPC3 (FPC-P1 or FPC-P2), or PTX1K platforms
  4. Check for recent MPC/line card restarts
    Run 'show log messages' and search for 'FPC' or 'MPC' crash indicators, or use 'show system crash' to review recent restart events
    Affected if MPC or line card restarts correlate with MPLS traffic patterns or are unexplained

The environment is affected if the device runs a vulnerable Junos version (15.1-17.4 series) AND has MPLS enabled AND uses affected hardware (MPC7/8/9, PTX-FPC3, or PTX1K line cards).

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 vendor-supplied Junos OS patches to the specified versions (15.1F6-S10, 15.1R7, 16.1R7, 17.4R2 or later) for affected releases. If patching is not immediately possible, consider filtering or rate-limiting MPLS traffic as a temporary workaround.

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-0030 — 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-0030 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