CVE-2025-20174
Cisco Ios Xe 16.1.1 … 3.18.9sp
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:HSummary
CVE-2025-20174 is a high-severity Buffer Access with Incorrect Length Value (CWE-805) vulnerability in Cisco Ios Xe. Its CVSS base score is 7.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-20174 is a vulnerability in the SNMP subsystem of Cisco IOS Software and Cisco IOS XE Software that stems from improper error handling when parsing SNMP requests. This flaw affects SNMP versions 1, 2c, and 3, enabling an authenticated, remote attacker to trigger a denial-of-service (DoS) condition by sending a crafted SNMP request to an affected device. Successful exploitation causes the device to reload unexpectedly, disrupting network operations. The vulnerability has a CVSS v3.1 base score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H) and is associated with CWE-805.
An authenticated remote attacker can exploit this vulnerability if they possess the necessary SNMP access credentials. For SNMP v2c or earlier versions, the attacker requires a valid read-write or read-only SNMP community string for the affected system. For SNMP v3, valid SNMP user credentials are needed. Once authenticated, the attacker sends a specially crafted SNMP request, leading to improper error handling that forces the device to reload and results in a DoS condition with high availability impact due to the scoped attack vector.
The Cisco Security Advisory provides detailed information on mitigation strategies and available patches for this vulnerability, accessible at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-snmp-dos-sdxnSUcW.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-2166
Vulnerability Data
A vulnerability in the SNMP subsystem of Cisco IOS Software and Cisco IOS XE Software could allow an authenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to improper error handling when parsing…
more
SNMP requests. An attacker could exploit this vulnerability by sending a crafted SNMP request to an affected device. A successful exploit could allow the attacker to cause the device to reload unexpectedly, resulting in a DoS condition. This vulnerability affects SNMP versions 1, 2c, and 3. To exploit this vulnerability through SNMP v2c or earlier, the attacker must know a valid read-write or read-only SNMP community string for the affected system. To exploit this vulnerability through SNMP v3, the attacker must have valid SNMP user credentials for the affected system.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and static analysis) directly finds incorrect length values used in sequential buffer accesses.
Secure engineering principles require explicit bounds checking and correct length calculations when performing buffer operations.
Input validation rejects or corrects malformed length values supplied from external sources before they reach buffer operations.
Memory protection mechanisms limit the blast radius when an incorrect length value causes an out-of-bounds access.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect out-of-bounds accesses, but does not guarantee prevention.
Secure development life cycle mandates buffer-safety practices that directly prevent incorrect length values.
Application security requirements can specify buffer-size validation, but do not prescribe implementation details.
Secure architecture principles encourage bounds-checked APIs, yet leave concrete coding decisions to developers.
Secure coding explicitly requires correct buffer-length handling, eliminating CWE-805 when followed.