Cisco Campus Gateway Software
Monthly
Authenticated attackers who already hold low-privileged access to a local or management interface of Cisco Meraki MR wireless access points, MV cameras, MX security appliances, or Cisco Campus Gateway Software can supply crafted input that the affected component fails to neutralize correctly, a CWE-74 injection-class condition rated CVSS 8.8 with scope change (S:C) and high confidentiality, integrity, and availability impact. Because the vector is AV:L with PR:L, the attacker must already be able to reach the device's management or local interface - exposure is tied to the management plane rather than the public internet - and the flaws were identified during a Cisco internal security review rather than through external reporting, with fixes delivered as software hardening releases described in Cisco advisory cisco-sa-hardening-meraki-os-drbEX9GH. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the specific vulnerable feature and exact affected firmware builds are not specified in the available data.
A bundled Cisco software-hardening release resolves multiple internally discovered resource-lifecycle flaws (CWE-664) affecting Cisco Meraki MX security appliances, MR wireless access points, MV camera firmware, and Cisco Campus Gateway Software. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), the impact is availability-only - an unauthenticated remote attacker who can reach the affected service can trigger resource mismanagement that crashes or degrades the device, with no confidentiality or integrity loss. No public exploit code or confirmed active exploitation has been identified at time of analysis, and Cisco has not published a specific patched firmware version in the CVE metadata, so administrators should consult the linked advisory to map the hardening release to their exact hardware and firmware train.
Incorrect-calculation flaws in Cisco's hardening release for Meraki MR wireless access points, MV cameras, MX security appliances, and Campus Gateway software allow an unauthenticated attacker on an adjacent network segment to achieve high impact to confidentiality, integrity, and availability (CVSS 8.8). Because the vector is AV:A/AC:L/PR:N/UI:N, exploitation requires the attacker to already sit in the same Layer-2 broadcast domain, management VLAN, or directly connected segment as the target device - it is not reachable from an arbitrary internet host, and that adjacency requirement is the principal limiting factor. No public exploit identified at time of analysis, and Cisco states the issues were discovered through its own proactive internal security review rather than through exploitation, so real-world urgency is moderate despite the high base score.
Cisco Meraki MR wireless access point software, MX security appliance firmware, MV camera firmware, and Cisco Campus Gateway Software can be crashed by an unauthenticated attacker positioned on the same Layer-2 adjacency (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H, base 7.4) due to insufficient control flow management (CWE-691) fixed in a vendor hardening release. Exploitation is confined to attackers with an existing local foothold or wireless/physical proximity; it is not reachable from a routed or internet position, and the assessed impact is availability loss only, with no confidentiality or integrity compromise. There is no public exploit identified at time of analysis and no CISA KEV listing; the flaw was discovered through Cisco's internal security review rather than through exploitation reporting.
Improper input validation in Cisco Meraki MR wireless access point, MV camera, and MX security appliance firmware - together with Cisco Campus Gateway Software - allows unauthenticated remote attackers to feed crafted input that the affected device fails to validate, producing a high integrity impact and a limited availability impact (C:N/I:H/A:L) under the assessed CVSS 3.1 vector. The issue is one of a set of CWE-20 weaknesses remediated in a single Cisco internal-hardening firmware release, so the specific vulnerable feature, protocol, or interface is not named and the affected version boundaries must be taken from the Cisco advisory. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); note that the 'Information Disclosure' tag does not align with the assessed vector, which shows no confidentiality impact.
Adjacent-network buffer management flaws in Cisco Meraki OS let an unauthenticated attacker within Layer 2 or wireless range trigger memory-safety failures on Cisco Meraki MR wireless access points, MV cameras, MX appliances, and Campus Gateway software, with the grouped advisory rated CVSS 9.6 (scope change plus high confidentiality, integrity, and availability impact). Exploitation requires the attacker to already sit on the same broadcast domain, Layer 2 segment, or RF coverage area - the flaw is not reachable from the routed internet - and the hardening bulletin does not disclose which protocol or feature actually triggers the CWE-119 condition. No public exploit code or confirmed active exploitation was identified at time of analysis; the fix ships as part of a vendor internal hardening release rather than a discrete single-version patch.
Improper access control in Cisco Meraki firmware - spanning MR wireless access point software, MX security appliance firmware, MV camera firmware, and Cisco Campus Gateway Software - lets an attacker positioned on an adjacent Layer 2 or wireless segment bypass authentication and reach protected functionality, with the highest impact on confidentiality. No credentials (PR:N) and no user interaction (UI:N) are required, attack complexity is low, and the Cisco-assigned score is 8.8 because the flaw crosses a security boundary (S:C); however, the attack is not routable from the internet, so real-world exposure is limited to whoever already shares a segment with the device, and no public exploit code or confirmed active exploitation was identified at time of analysis. Cisco addressed the issue in a proactive internal hardening release and published advisory cisco-sa-hardening-meraki-os-drbEX9GH, which should be used to confirm exact affected firmware versions because the advisory bundles several internally discovered issues.
Authenticated attackers who already hold low-privileged access to a local or management interface of Cisco Meraki MR wireless access points, MV cameras, MX security appliances, or Cisco Campus Gateway Software can supply crafted input that the affected component fails to neutralize correctly, a CWE-74 injection-class condition rated CVSS 8.8 with scope change (S:C) and high confidentiality, integrity, and availability impact. Because the vector is AV:L with PR:L, the attacker must already be able to reach the device's management or local interface - exposure is tied to the management plane rather than the public internet - and the flaws were identified during a Cisco internal security review rather than through external reporting, with fixes delivered as software hardening releases described in Cisco advisory cisco-sa-hardening-meraki-os-drbEX9GH. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the specific vulnerable feature and exact affected firmware builds are not specified in the available data.
A bundled Cisco software-hardening release resolves multiple internally discovered resource-lifecycle flaws (CWE-664) affecting Cisco Meraki MX security appliances, MR wireless access points, MV camera firmware, and Cisco Campus Gateway Software. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), the impact is availability-only - an unauthenticated remote attacker who can reach the affected service can trigger resource mismanagement that crashes or degrades the device, with no confidentiality or integrity loss. No public exploit code or confirmed active exploitation has been identified at time of analysis, and Cisco has not published a specific patched firmware version in the CVE metadata, so administrators should consult the linked advisory to map the hardening release to their exact hardware and firmware train.
Incorrect-calculation flaws in Cisco's hardening release for Meraki MR wireless access points, MV cameras, MX security appliances, and Campus Gateway software allow an unauthenticated attacker on an adjacent network segment to achieve high impact to confidentiality, integrity, and availability (CVSS 8.8). Because the vector is AV:A/AC:L/PR:N/UI:N, exploitation requires the attacker to already sit in the same Layer-2 broadcast domain, management VLAN, or directly connected segment as the target device - it is not reachable from an arbitrary internet host, and that adjacency requirement is the principal limiting factor. No public exploit identified at time of analysis, and Cisco states the issues were discovered through its own proactive internal security review rather than through exploitation, so real-world urgency is moderate despite the high base score.
Cisco Meraki MR wireless access point software, MX security appliance firmware, MV camera firmware, and Cisco Campus Gateway Software can be crashed by an unauthenticated attacker positioned on the same Layer-2 adjacency (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H, base 7.4) due to insufficient control flow management (CWE-691) fixed in a vendor hardening release. Exploitation is confined to attackers with an existing local foothold or wireless/physical proximity; it is not reachable from a routed or internet position, and the assessed impact is availability loss only, with no confidentiality or integrity compromise. There is no public exploit identified at time of analysis and no CISA KEV listing; the flaw was discovered through Cisco's internal security review rather than through exploitation reporting.
Improper input validation in Cisco Meraki MR wireless access point, MV camera, and MX security appliance firmware - together with Cisco Campus Gateway Software - allows unauthenticated remote attackers to feed crafted input that the affected device fails to validate, producing a high integrity impact and a limited availability impact (C:N/I:H/A:L) under the assessed CVSS 3.1 vector. The issue is one of a set of CWE-20 weaknesses remediated in a single Cisco internal-hardening firmware release, so the specific vulnerable feature, protocol, or interface is not named and the affected version boundaries must be taken from the Cisco advisory. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); note that the 'Information Disclosure' tag does not align with the assessed vector, which shows no confidentiality impact.
Adjacent-network buffer management flaws in Cisco Meraki OS let an unauthenticated attacker within Layer 2 or wireless range trigger memory-safety failures on Cisco Meraki MR wireless access points, MV cameras, MX appliances, and Campus Gateway software, with the grouped advisory rated CVSS 9.6 (scope change plus high confidentiality, integrity, and availability impact). Exploitation requires the attacker to already sit on the same broadcast domain, Layer 2 segment, or RF coverage area - the flaw is not reachable from the routed internet - and the hardening bulletin does not disclose which protocol or feature actually triggers the CWE-119 condition. No public exploit code or confirmed active exploitation was identified at time of analysis; the fix ships as part of a vendor internal hardening release rather than a discrete single-version patch.
Improper access control in Cisco Meraki firmware - spanning MR wireless access point software, MX security appliance firmware, MV camera firmware, and Cisco Campus Gateway Software - lets an attacker positioned on an adjacent Layer 2 or wireless segment bypass authentication and reach protected functionality, with the highest impact on confidentiality. No credentials (PR:N) and no user interaction (UI:N) are required, attack complexity is low, and the Cisco-assigned score is 8.8 because the flaw crosses a security boundary (S:C); however, the attack is not routable from the internet, so real-world exposure is limited to whoever already shares a segment with the device, and no public exploit code or confirmed active exploitation was identified at time of analysis. Cisco addressed the issue in a proactive internal hardening release and published advisory cisco-sa-hardening-meraki-os-drbEX9GH, which should be used to confirm exact affected firmware versions because the advisory bundles several internally discovered issues.