dbcve.org
Meraki Mr 24 FirmwareOperating system · Cisco

CVE-2018-0284

MEDIUM · 6.5 CVSS v3.0 Published 2018-11-08
Fix available
A fix is available. Upgrade to 9.37 / 10.20 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
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.

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 · moderate confidence

A vulnerability in the local status page functionality of Cisco Meraki MR, MS, MX, Z1, and Z3 product lines allows an authenticated, remote attacker to modify device configuration files and establish an interactive session with elevated privileges, potentially leading to further device compromise and data exfiltration.

MitigationRestrict access to the local status page to trusted management networks only, ensure strong authentication controls are in place for administrative access, and apply vendor patches when available. Consider network segmentation to limit exposure of management interfaces.

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
Meraki Mr 24 FirmwareOperating system
Affected:< 24.13
Meraki Mr 25 FirmwareOperating system
Affected:< 25.11
Meraki Ms 10 FirmwareOperating system
Affected:< 10.20
Meraki Ms 9 FirmwareOperating system
Affected:< 9.37
Meraki Mx 13 FirmwareOperating system
Affected:< 13.32
Meraki Mx 14 FirmwareOperating system
Affected:< 14.25
Meraki Mx 15 FirmwareOperating system
Affected:< 15.7

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 Meraki device model
    Access the Meraki Dashboard or check the physical device label to determine if the device is an MR (wireless), MS (switch), MX (security appliance), Z1, or Z3 model.
    Affected if The device is one of these models: MR, MS, MX, Z1, or Z3.
  2. Determine the firmware version
    Log into the Meraki Dashboard, navigate to the device inventory, and check the firmware version displayed for the affected device. Alternatively, access the device local status page and review the firmware version shown there.
    Affected if The firmware version falls within the affected ranges: MR 24 < 24.13, MR 25 < 25.11, MS 10 < 10.20, MS 9 < 9.37, MX 13 < 13.32, MX 14 < 14.25, MX 15 < 15.7.
  3. Verify if local status page is accessible
    Attempt to access the local status page of the Meraki device from a remote network location. The local status page is typically accessed via HTTP/HTTPS to the device's management IP address. Check if the page loads without requiring VPN or local network access.
    Affected if The local status page is accessible from untrusted networks, meaning the device is affected if other conditions are met.
  4. Confirm authentication requirements for local status page
    Review the device configuration in the Meraki Dashboard under Organization > Settings > Local status page access. Check whether the local status page requires authentication or is open to anonymous access.
    Affected if The local status page is enabled and accessible without proper authentication controls, making the device vulnerable to exploitation.

A device is affected if it is an MR, MS, MX, Z1, or Z3 model running a firmware version lower than the fixed releases AND the local status page is accessible to untrusted networks or lacks adequate authentication controls.

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
Upgrade available Upgrade to 9.37 / 10.20 / 13.32 or later
Fixed in 9.3710.2013.32
Interim mitigation

Restrict access to the local status page to trusted management networks only, ensure strong authentication controls are in place for administrative access, and apply vendor patches when available. Consider network segmentation to limit exposure of management interfaces.

Fix this in Meraki Mr 24 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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