CVE-2017-6627

mediumpriority · act · 90OT risk · criticalKEV · exploitedEPSS 0.062 · 93 %ileEURUUS

grimoire priorityP0 · Act now

Exploitable?

Yes · in the wild

CISA KEV

Likely / severe?

6.16% (93rd) EPSS

CVSS 5 · medium

Is it mine?

120 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · fstec_bdu · cisco_csaf

added 2022-03-03remediate by 2022-03-24

required action Apply updates per vendor instructions.

EPSS · scored 2026-10-26

Cisco IOS Software and Cisco IOS XE Software UDP Packet Processing Denial-of-Service Vulnerability

A vulnerability in the UDP processing code of Cisco IOS 15.1, 15.2, and 15.4 and IOS XE 3.14 through 3.18 could allow an unauthenticated, remote attacker to cause the input queue of an affected system to hold UDP packets, causing an interface queue wedge and a denial of service (DoS) condition. The vulnerability is due to Cisco IOS Software application changes that create UDP sockets and leave the sockets idle without closing them. An attacker could exploit this vulnerability by sending UDP packets with a destination port of 0 to an affected device. A successful exploit could allow the attacker to cause UDP packets to be held in the input interfaces queue, resulting in a DoS condition. The input interface queue will stop holding UDP packets when it receives 250 packets. Cisco Bug IDs: CSCup10024, CSCva55744, CSCva95506.

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

Fixed3.14.0Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.14.1Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.14.2Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.14.3Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.14.4Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.15.0Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.15.1Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.15.1cScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.15.2Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.15.3Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.15.4Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.0Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.0aScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.0bScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.0cScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.1Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.1aScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.2Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.2aScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.2bScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.3Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.3aScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.4Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.4aScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.4bScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.4cScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.4dScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.4eScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.4gScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.5Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.5aScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.5bScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.16.6Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.17.0Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.17.1Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.17.1aScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.17.2Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.17.3Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.18.0Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.18.0aScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.18.1Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.18.2Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed3.18.3Scisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
FixedCisco IOScisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Workaround3.14.0Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.14.1Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.14.2Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.14.3Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.14.4Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.15.0Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.15.1Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.15.1cScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.15.2Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.15.3Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.15.4Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.0Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.0aScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.0bScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.0cScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.1Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.1aScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.2Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.2aScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.2bScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.3Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.3aScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.4Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.4aScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.4bScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.4cScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.4dScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.4eScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.4gScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.5Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.5aScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.5bScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.16.6Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.17.0Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.17.1Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.17.1aScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.17.2Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.17.3Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.18.0Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.18.0aScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.18.1Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.18.2Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
Workaround3.18.3Scisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0
WorkaroundCisco IOScisco_csaf
To work around this vulnerability, administrators can set a maximum hold queue value that is greater than 250 for all device interfaces. The following example shows how to set the value to 350 by using the hold queue in interface configuration command: Router# configure terminal Router(config)# interface gigabitEthernet 1 Router(config-if)# hold-queue 350 in Administrators can also configure an access-control list (ACL) that blocks UDP packets with a destination port of 0 and apply the ACL to all device interfaces, for example: Extended IP access list 180 10 deny udp any any eq 0

cvss

Technical severity, 0–10. One row per scoring source.

7.5

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5–7.5

v2.05mediumAV:N/AC:L/Au:N/C:N/I:N/A:Pprimary · NVD / NIST USexploitability 10 · impact 2.9

v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hprimary · NVD / NIST USexploitability 3.9 · impact 3.6

v3.05.3mediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lsecondary · Cisco PSIRT US

v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:Hsecondary · CVSS-BT (t0sche)

v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · ENISA EU

v3.17.5highAV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · FSTEC (BDU) RU

v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondaryexploitability 3.9 · impact 3.6

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: active · Automatable: yes · Technical Impact: partialcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-404USprimaryCWE-399USCWE-399US

affected products (120)

Products and version ranges known to be affected.

showing 20 of 120

advisories (1)

Vendor and ecosystem advisories describing this.

cisco-sa-20170906-ios-udpCisco IOS and Cisco IOS XE Software UDP Packet Processing Denial of Service Vulnerability2017-09-06csaf · cisco_csafUS
A vulnerability in the UDP processing code of Cisco IOS and Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause the input queue of an affected system to hold UDP packets, causing an interface queue wedge and a denial of service (DoS) condition. The vulnerability is due to Cisco IOS Software application changes that create UDP sockets and leave the sockets idle without closing them. An attacker could exploit this vulnerability by sending UDP packets with a destination port of 0 to an affected device. A successful exploit could allow the attacker to cause UDP packets to be held in the input interfaces queue, resulting in a DoS condition. The input interface queue will stop holding UDP packets when it receives 250 packets. There are workarounds that address this vulnerability.

also known as (4)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd fstec_bdu cisco_csaf NVD CVE.org MITRE

published 2017-09-07modified 2026-06-17

related (2,015)

Related entries.

ID	severity	EPSS	exploitable	published
CVE-2023-38180US	—OT critical	14.1% (97th)	KEV	2023-08-08
.NET and Visual Studio Denial of Service Vulnerability
CVE-2018-8639US	high7.8OT critical	22.2% (98th)	KEV	2018-12-12
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka "Win32k Elevation of Privilege Vulnerability." T…
CVE-2018-8611US	high7.8OT critical	4.20% (91st)	KEV	2018-12-12
An elevation of privilege vulnerability exists when the Windows kernel fails to properly handle objects in memory, aka "Windows Kernel Elevation of Privilege Vulnerability." This a…
CVE-2018-8406US	high7.8OT critical	3.44% (89th)	KEV	2018-08-15
An elevation of privilege vulnerability exists when the DirectX Graphics Kernel (DXGKRNL) driver improperly handles objects in memory, aka "DirectX Graphics Kernel Elevation of Pri…
CVE-2018-8405US	high7.8OT critical	3.44% (89th)	KEV	2018-08-15
An elevation of privilege vulnerability exists when the DirectX Graphics Kernel (DXGKRNL) driver improperly handles objects in memory, aka "DirectX Graphics Kernel Elevation of Pri…

+2010 more

references (10)

External citations — patches, advisories, analysis.

http://www.securitytracker.com/id/1039289 cnnvd
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20170906-ios-udp cnnvd
https://www.securityfocus.com/bid/100644 cnnvd
http://www.securityfocus.com/bid/100644 enisa_euvd
http://www.securitytracker.com/id/1039289 enisa_euvd
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20170906-ios-udp enisa_euvd
http://www.securityfocus.com/bid/100644Broken LinkThird Party AdvisoryVDB Entrynvd
http://www.securitytracker.com/id/1039289Broken LinkThird Party AdvisoryVDB Entrynvd

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan