dbcve.org
Meraki Mr FirmwareApplication · Cisco

CVE-2014-7994

MEDIUM · 5.4 CVSS v2.0 Published 2014-12-24
Fix available
A fix is available. Upgrade to after 2014-09-24 or later.
See remediation →
59/100
Remediation priority · Elevated
No privileges 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
Cisco-Meraki MS, MR, and MX devices with firmware before 2014-09-24 allow remote attackers to execute arbitrary commands by leveraging knowledge of a cross-device secret and a per-device secret, and sending a request to an unspecified HTTP handler on the local network, aka Cisco-Meraki defect ID 00301991.

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

This vulnerability in Cisco-Meraki MS, MR, and MX devices running firmware predating September 24, 2014 allows remote attackers with knowledge of both a cross-device secret and a per-device secret to execute arbitrary commands by sending requests to an undocumented HTTP handler on the local network. The command injection stems from insufficient validation of these secrets when processing HTTP requests.

MitigationUpgrade all affected Meraki devices (MS, MR, MX) to firmware released on or after 2014-09-24. Additionally, change any default secrets from initial configuration and restrict network access to local 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 FirmwareApplication
Affected:<= 2014-09-24
Meraki MrHardware / appliance
Affected:all versions
Meraki Mx FirmwareApplication
Affected:<= 2014-09-24
Meraki MxHardware / appliance
Affected:all versions
Meraki Ms FirmwareApplication
Affected:<= 2014-09-24
Meraki MsHardware / appliance
Affected:all versions

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
Adjacent
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:A/AC:M/Au:N/C:P/I:P/A:P

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 Meraki device model
    Access the Meraki dashboard or check the device label to confirm the model is an MS (switch), MR (wireless access point), or MX (security appliance)
    Affected if Device is not an MS, MR, or MX model
  2. Check firmware version
    Log into the Meraki dashboard, navigate to the device organization, and check the firmware version under the device status or firmware section
    Affected if Firmware version date is on or before September 24, 2014 (versions released before 2014-09-24)
  3. Verify undocumented HTTP handler accessibility
    From a host on the same local network, attempt to access the undocumented HTTP handler endpoint (no specific path provided in advisory - compare your environment to known vulnerability scanner results for this CVE)
    Affected if The undocumented HTTP handler responds to local network requests without proper authentication
  4. Assess secret configuration
    Review device configuration for the cross-device secret and per-device secret settings, checking whether default or weak secrets from initial setup remain in use
    Affected if Default or easily guessable cross-device and per-device secrets are configured and could be obtained by an attacker
  5. Check local network exposure
    Determine if the local management interface is accessible from untrusted network segments by reviewing firewall rules and access control lists
    Affected if Local management interfaces are accessible from network segments beyond the trusted administrative network

A user is affected if they have a Meraki MS, MR, or MX device running firmware released on or before September 24, 2014 (or all versions per vendor scope) with the undocumented HTTP handler accessible and default/weak secrets in use on the local network.

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 a release after 2014-09-24
Interim mitigation

Upgrade all affected Meraki devices (MS, MR, MX) to firmware released on or after 2014-09-24. Additionally, change any default secrets from initial configuration and restrict network access to local management interfaces.

Fix this in Meraki Mr Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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