CVE-2018-0063 json
Junos OS: Nexthop index allocation failed: private index space exhausted after incoming ARP requests to management interface
published 2018-10-10 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-0887
- cvss
- 6.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
A vulnerability in the IP next-hop index database in Junos OS 17.3R3 may allow a flood of ARP requests, sent to the management interface, to exhaust the private Internal routing interfaces (IRIs) next-hop limit. Once the IRI next-hop database is full, no further next hops can be learned and existing entries cannot be cleared, leading to a sustained denial of service (DoS) condition. An indicator of compromise for this issue is the report of the following error message: %KERN-4: Nexthop index allocation failed: private index space exhausted This issue only affects the management interface, and does not impact regular transit traffic through the FPCs. This issue also only affects Junos OS 17.3R3. No prior versions of Junos OS are affected by this issue. Affected releases are Juniper Networks Junos OS: 17.3R3.
Patch / fix
- Juniper Networks Junos OS 17.3R3-S1
Exploit prediction
0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.5 | CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 3.3 | AV:A/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- Juniper Networks Junos OS
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
kb.juniper.net
/JSA10899
vendor-advisory
-
securitytracker.com
/id/1041861
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-0063
- NVD CVE-2018-0063
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.