JunosOperating system · Juniper

CVE-2018-0054

MEDIUM · 6.5 CVSS v3.0 Published 2018-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
On QFX5000 Series and EX4600 switches, a high rate of Ethernet pause frames or an ARP packet storm received on the management interface (fxp0) can cause egress interface congestion, resulting in routing protocol packet drops, such as BGP, leading to peering flaps. The following log message may also be displayed: fpc0 dcbcm_check_stuck_buffers: Buffers are stuck on queue 7 of port 45 This issue only affects the QFX5000 Series products (QFX5100, QFX5110, QFX5200, QFX5210) and the EX4600 switch. No other platforms are affected by this issue. Affected releases are Juniper Networks Junos OS: 14.1X53 versions prior to 14.1X53-D47 on QFX5000 Series and EX4600; 15.1 versions prior to 15.1R7, 15.1R8 on QFX5000 Series and EX4600; 15.1X53 versions prior to 15.1X53-D233 on QFX5000 Series and EX4600; 16.1 versions prior to 16.1R7 on QFX5000 Series and EX4600; 16.2 versions prior to 16.2R3 on QFX5000 Series and EX4600; 17.1 versions prior to 17.1R2-S9, 17.1R3 on QFX5000 Series and EX4600; 17.2 versions prior to 17.2R2-S6, 17.2R3 on QFX5000 Series and EX4600; 17.2X75 versions prior to 17.2X75-D42 on QFX5000 Series and EX4600; 17.3 versions prior to 17.3R3 on QFX5000 Series and EX4600; 17.4 versions prior to 17.4R2 on QFX5000 Series and EX4600; 18.1 versions prior to 18.1R2 on QFX5000 Series and EX4600.

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

On QFX5000 Series switches and EX4600, a high rate of Ethernet pause frames or ARP packet storm received on the management interface (fxp0) causes egress interface congestion, leading to routing protocol packet drops such as BGP and resulting in peering flaps. The issue stems from shared buffer resources between management and data plane traffic.

MitigationUpgrade to the fixed Junos OS versions (14.1X53-D47, 15.1R7/R8, 15.1X53-D233, 16.1R7, 16.2R3, 17.1R2-S9/17.1R3, 17.2R2-S6/17.2R3, 17.2X75-D42, 17.3R3, 17.4R2, 18.1R2). As a workaround, implement rate-limiting on the management interface or filter excessive ARP traffic to prevent the storm.

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:= 14.1x53= 15.1= 15.1x53= 16.1= 16.2= 17.1= 17.2= 17.2x75= 17.3= 17.4= 18.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:A/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 the switch model
    Run 'show chassis hardware' or 'show system information' to confirm the device is a QFX5000 Series switch or EX4600
    Affected if The hardware model is QFX5000 Series or EX4600
  2. Check the installed Junos version
    Run 'show version' to display the Junos OS version
    Affected if The version matches or falls within: 14.1x53, 15.1, 15.1x53, 16.1, 16.2, 17.1, 17.2, 17.2x75, 17.3, 17.4, or 18.1
  3. Verify management interface fxp0 status
    Run 'show interfaces fxp0' to confirm the management interface is configured and active
    Affected if The management interface fxp0 is in use
  4. Review BGP peer status for flaps
    Run 'show bgp summary' and check for peer state changes or drops, especially during periods of high management traffic
    Affected if BGP peers are experiencing unexpected flaps or drops
  5. Check for ARP traffic anomalies
    Monitor management interface traffic with 'show interfaces fxp0 statistics' or external packet capture to identify ARP packet storms
    Affected if Abnormally high ARP traffic or Ethernet pause frames are observed on fxp0

A user is affected if they run an unpatched Junos version (14.1x53 through 18.1) on QFX5000 or EX4600 hardware and experience BGP peer flaps correlated with high ARP or pause frame activity on the management interface.

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 (14.1X53-D47, 15.1R7/R8, 15.1X53-D233, 16.1R7, 16.2R3, 17.1R2-S9/17.1R3, 17.2R2-S6/17.2R3, 17.2X75-D42, 17.3R3, 17.4R2, 18.1R2). As a workaround, implement rate-limiting on the management interface or filter excessive ARP traffic to prevent the storm.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-0054 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