CyberSecBulletin
CVE-2025-20175NVD status: Analyzed

IOS: Buffer Access with Incorrect Length Value

Published Updated By the CyberSecBulletin desk

CVE-2025-20175 is a high-severity buffer access with incorrect length value vulnerability in IOS from Cisco, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected IOS versions: 12.2(53)SE1; 12.2(55)SE; 12.2(50)SE2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.76% chance of exploitation within 30 days, higher than 56% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of IOS you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on sec.cloudapps.cisco.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
CiscoIOS12.2(53)SE1; 12.2(55)SE; 12.2(50)SE2; 12.2(50)SE1; 12.2(50)SE5; 12.2(53)SE; 12.2(55)SE3; 12.2(55)SE2; and 32 more rangesNot stated
CiscoCisco IOS XE Software3.2.0SG; 3.2.1SG; 3.2.2SG; 3.2.3SG; 3.2.4SG; 3.2.5SG; 3.2.6SG; 3.2.7SG; and 32 more rangesNot stated
CiscoiOS Xe3.2.0se; 3.2.0sg; 3.2.1se; 3.2.1sg; 3.2.2se; 3.2.2sg; 3.2.3se; 3.2.3sg; and 32 more rangesNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H. Scored by CNA (cisco.com).

Official description

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 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Buffer Access with Incorrect Length Value

The product uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Buffer Access with Incorrect Length Value vulnerabilities (CWE-805)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in IOS

All IOS vulnerabilities

Recent Buffer Access with Incorrect Length Value vulnerabilities

Spotted an error? Tell us.