CVE-2018-0284 json
Cisco Meraki Local Status Page Privilege Escalation Vulnerability
published 2018-11-08 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-1107
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
A vulnerability in the local status page functionality of the Cisco Meraki MR, MS, MX, Z1, and Z3 product lines could allow an authenticated, remote attacker to modify device configuration files. The vulnerability occurs when handling requests to the local status page. An exploit could allow the attacker to establish an interactive session to the device with elevated privileges. The attacker could then use the elevated privileges to further compromise the device or obtain additional configuration data from the device that is being exploited.
Patch / fix
- cisco meraki_mr_24_firmware 24.13
- cisco meraki_mr_25_firmware 25.11
- cisco meraki_ms_10_firmware 10.20
- cisco meraki_ms_9_firmware 9.37
- cisco meraki_mx_13_firmware 13.32
- cisco meraki_mx_14_firmware 14.25
- cisco meraki_mx_15_firmware 15.7
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
Affected products
- Cisco Cisco Meraki MR
- Cisco Cisco Meraki M5
- Cisco Cisco Meraki MX
- Cisco Cisco Meraki Z1
- Cisco Cisco Meraki Z3
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
tools.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-20181107-meraki
vendor-advisory
-
securityfocus.com
/bid/105878
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-0284
- NVD CVE-2018-0284
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.