dbcve.org
JunosOperating system · Juniper

CVE-2018-0029

MEDIUM · 6.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 →
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
While experiencing a broadcast storm, placing the fxp0 interface into promiscuous mode via the 'monitor traffic interface fxp0' can cause the system to crash and restart (vmcore). This issue only affects Junos OS 15.1 and later releases, and affects both single core and multi-core REs. Releases prior to Junos OS 15.1 are unaffected by this vulnerability. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1F6-S11, 15.1R4-S9, 15.1R6-S6, 15.1R7; 15.1X49 versions prior to 15.1X49-D140; 15.1X53 versions prior to 15.1X53-D59 on EX2300/EX3400; 15.1X53 versions prior to 15.1X53-D67 on QFX10K; 15.1X53 versions prior to 15.1X53-D233 on QFX5200/QFX5110; 15.1X53 versions prior to 15.1X53-D471, 15.1X53-D490 on NFX; 16.1 versions prior to 16.1R3-S8, 16.1R5-S4, 16.1R6-S1, 16.1R7; 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-S6, 17.2R2-S4, 17.2R3; 17.2X75 versions prior to 17.2X75-D90, 17.2X75-D110; 17.3 versions prior to 17.3R1-S4, 17.3R2; 17.4 versions prior to 17.4R1-S3, 17.4R2.

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

During a broadcast storm, placing the fxp0 interface into promiscuous mode using the 'monitor traffic interface fxp0' command causes Junos OS to crash and restart, generating a vmcore dump. This is a denial-of-service vulnerability affecting Junos OS 15.1 and later on both single-core and multi-core Routing Engines.

MitigationAvoid using the 'monitor traffic interface fxp0' command during broadcast storm conditions, or upgrade to the fixed Junos OS versions specified in the advisory (15.1F6-S11, 15.1R4-S9, 15.1R6-S6, 15.1R7, 15.1X49-D140, etc.).

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.1x49= 15.1x53= 16.1= 16.2= 17.1= 17.2x75= 17.3= 17.4= 17.2

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 Junos OS version
    Run 'show version' or 'show version detail' to obtain the installed Junos OS version
    Affected if The version matches any of these: 15.1, 15.1x49, 15.1x53, 16.1, 16.2, 17.1, 17.2, 17.2x75, 17.3, or 17.4
  2. Verify fxp0 interface exists
    Run 'show interfaces fxp0' or 'show interfaces terse | grep fxp0' to confirm the fxp0 interface is present on the device
    Affected if The fxp0 interface exists on the device
  3. Check for recent monitor traffic usage on fxp0
    Review system logs (log files in /var/log/) or use 'show log messages' to search for entries containing 'monitor traffic interface fxp0' or similar patterns
    Affected if The 'monitor traffic interface fxp0' command was recently executed on the device
  4. Look for crash dumps or unexpected restarts
    Check for vmcore files in /var/crash/ or use 'show system core-dumps' and review 'show system reboot' for unexpected restart events
    Affected if A vmcore dump or unexpected system restart occurred following broadcast storm conditions while fxp0 was in promiscuous mode via the monitor traffic command

The device is affected if it runs a vulnerable Junos version (15.1 through 17.4 series), has an fxp0 interface, and the 'monitor traffic interface fxp0' command was used during a broadcast storm that caused a crash or vmcore dump.

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

Avoid using the 'monitor traffic interface fxp0' command during broadcast storm conditions, or upgrade to the fixed Junos OS versions specified in the advisory (15.1F6-S11, 15.1R4-S9, 15.1R6-S6, 15.1R7, 15.1X49-D140, etc.).

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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