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

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

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

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through an adjacent network may attempt exploitation without authentication after a user interaction. If successful, the issue may disrupt the affected service.

What

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through an adjacent network may attempt exploitation without authentication after a user interaction. If successful, the issue may disrupt the affected service.

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: an adjacent network → Uncontrolled Resource Consumption → disrupt the affected service
Attack surface: Adjacent
Privileges required: None: unauthenticated exploitation is possible
User interaction: Required interaction required
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-400 ↗
CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

UnauthenticatedDenial of serviceCWE-400

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2018-0853Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

Canadian Centre for Cyber Security · English · AV18-116Juniper security bulletins

-2016-8618, CVE-2016-8619, CVE-2016-8620, CVE-2016-8621, CVE-2016-8622, CVE-2016-8623, CVE-2016-8624, CVE-2016-8625, CVE-2017-3145, CVE-2018-2579, CVE-2018-2588, CVE-2018-2599, CVE-2018-2603, CVE-2018-2618, CVE-2018-2629, CVE-2018-2633, CVE-2018-2637, CVE-2018-2663, CVE-2018-2678, CVE-2017-12613, CVE-2017-10198, 2017-10281, CVE-2017-10295, CVE-2017-10345, CVE-2017-10355, CVE-2017-10356, CVE-2017-10388, CVE-2017-15896, CVE-2017-5753, CVE-2017-5715, CVE-2017-5754, CVE-2018-0039, CVE-2018-0040, CVE-2018-0042, CVE-2018-0038, CVE-2018-0041, CVE-2018-1000115, CVE-2018-0037, CVE-2018-0034, CVE-2018-0035, CVE-2018-0032, CVE-2018-0031, CVE-2018-0030, CVE-2018-0029, CVE-2018-0027, CVE-2018-0026, CVE-2018-0025, CVE-2018-0024, CVE-2015-7236 Suggested action CCIRC recommends that system administrators test and deploy the vendor-released updates to affected applications accordingly. References https://kb.juniper.net/InfoCenter/index?page=content&id=JSA10803&cat=SIRT_1&actp=LIST https://kb.juniper.net/InfoCenter/index?page=content&id=JSA10857&cat=SIRT_1&actp=LIST https://kb.juniper.net/InfoCenter/index?page=content&id=JSA10858&cat=SIRT_1&actp=LIST https://kb.juniper.net/InfoCenter/index?page=content&id=JSA10859&cat=SIRT_1&actp=LIST https://kb.juniper.net/InfoCenter/index?page=content&id=JSA10860&cat=SIRT_1&

Official advisory ↗

CERT-FR · French · CERTFR-2018-AVI-339Multiples vulnérabilités dans les produits Juniper

.cve.org/CVERecord?id=CVE-2017-7407 Référence CVE CVE-2017-8816 https://www.cve.org/CVERecord?id=CVE-2017-8816 Référence CVE CVE-2017-8817 https://www.cve.org/CVERecord?id=CVE-2017-8817 Référence CVE CVE-2017-8818 https://www.cve.org/CVERecord?id=CVE-2017-8818 Référence CVE CVE-2017-9502 https://www.cve.org/CVERecord?id=CVE-2017-9502 Référence CVE CVE-2018-0024 https://www.cve.org/CVERecord?id=CVE-2018-0024 Référence CVE CVE-2018-0025 https://www.cve.org/CVERecord?id=CVE-2018-0025 Référence CVE CVE-2018-0026 https://www.cve.org/CVERecord?id=CVE-2018-0026 Référence CVE CVE-2018-0027 https://www.cve.org/CVERecord?id=CVE-2018-0027 Référence CVE CVE-2018-0029 https://www.cve.org/CVERecord?id=CVE-2018-0029 Référence CVE CVE-2018-0030 https://www.cve.org/CVERecord?id=CVE-2018-0030 Référence CVE CVE-2018-0031 https://www.cve.org/CVERecord?id=CVE-2018-0031 Référence CVE CVE-2018-0032 https://www.cve.org/CVERecord?id=CVE-2018-0032 Référence CVE CVE-2018-0034 https://www.cve.org/CVERecord?id=CVE-2018-0034 Référence CVE CVE-2018-0035 https://www.cve.org/CVERecord?id=CVE-2018-0035 Référence CVE CVE-2018-0037 https://www.cve.org/CVERecord?id=CVE-2018-0037 Référence CVE CVE-2018-0038 https://www.cve.org/CVERecord?id=CVE-2018-0038 Référence CVE CVE-2018-0039 https://www.cve.org/CVERecord?id=CVE-2018-0039 Ré

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2018-007997Juniper Networks Junos OS におけるリソースの枯渇に関する脆弱性

Juniper Networks Junos OS には、リソースの枯渇に関する脆弱性が存在します。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: Junos OS: 15.1 < 15.1F6-S11, 15.1R4-S9, 15.1R6-S6, 15.1R7, 16.1 < 16.1R3-S8, 16.1R5-S4, 16.1R6-S1, 16.1R7, 16.2 < 16.2R1-S6, 16.2R2-S5, 16.2R3, 17.1 < 17.1R1-S7, 17.1R2-S7, 17.1R3, 17.2 < 17.2R1-S6, 17.2R2-S4, 17.2R3, 17.2X75 < 17.2X75-D90, 17.2X75-D110, 17.3 < 17.3R1-S4, 17.3R2, 17.4 < 17.4R1-S3, 17.4R2, 15.1X49 < 15.1X49-D140, 15.1X53 < 15.1X53-D59, 15.1X53 < 15.1X53-D67, 15.1X53 < 15.1X53-D233, 15.1X53 < 15.1X53-D471, 15.1X53-D490
Fixed: The following software releases have been updated to resolve this specific issue: 15.1F6-S11*, 15.1R4-S9, 15.1R6-S6, 15.1R7, 15.1X49-D140, 15.1X53-D233, 15.1X53-D471, 15.1X53-D490, 15.1X53-D59, 15.1X53-D67, 16.1R3-S8, 16.1R5-S4, 16.1R6-S1, 16.1R7, 16.2R1-S6, 16.2R2-S5, 16.2R3, 17.1R1-S7, 17.1R2-S7, 17.1R3, 17.2R1-S6, 17.2R2-S4, 17.2R3, 17.2X75-D110, 17.2X75-D90, 17.3R1-S4, 17.3R2, 17.4R1-S3, 17.4R2, 18.1R1, 18.1X75-D10, and all subsequent releases.
*Future availability
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 11 Jul 2018 · Last source change 16 Sept 2024, 19:51 UTC · CWE-400 · Uncontrolled Resource Consumption

CVE recordCVE.org · 5.1

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-01

European sourceENISA EUVD · EUVD-2018-0853

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceNIST NVD

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

16 Sept 2024, 19:51 UTC
Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to authoritative remediation link · mitigation.
Before
no authoritative guidance recorded
After
authoritative remediation link · mitigation
af854a3a-2127-422b-91ae-364da2661108 ↗
16 Sept 2024, 19:51 UTC
Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
Before
Awaiting fix
After
Mitigation available
af854a3a-2127-422b-91ae-364da2661108 ↗
1 Sept 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2018-0853 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2018-0853"}
ENISA EUVD ↗
16 Sept 2024, 19:51 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2018-07-11CVE published

2024-09-16Mitigation reference recorded

ENISA EUVD · EUVD-2018-0853↗Mitigation reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Junos OS: Kernel crash (vmcore) during broadcast storm after enabling 'monitor traffic interface fxp0'

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2018-0853

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

Junos OS: Kernel crash (vmcore) during broadcast storm after enabling 'monitor traffic interface fxp0'

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2018-0853

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.