Cisco IOS and Cisco IOS XE Software UDP Packet Processing Denial of Service Vulnerability
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.
beschreibt (1)
Zugehörige CVEs.
| ID | Schweregrad | ausnutzbar | ||
|---|---|---|---|---|
| CVE-2017-6627US | high7.5OT kritisch | KEV | ||
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 o… | ||||
Referenzen
Externe Belege — Patches, Meldungen, Analysen.
Behebungen (88)
- Behoben3.14.0S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.14.1S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.14.2S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.14.3S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.14.4S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.15.0S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.15.1S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.15.1cS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.15.2S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.15.3S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.15.4S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.0S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.0aS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.0bS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.0cS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.1S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.1aS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.2S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.2aS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.2bS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.3S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.3aS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.4S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.4aS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.4bS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.4cS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.4dS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.4eS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.4gS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.5S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.5aS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.5bS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.16.6S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.17.0S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.17.1S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.17.1aS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.17.2S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.17.3S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.18.0S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.18.0aS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.18.1S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.18.2S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben3.18.3S
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - BehobenCisco IOS
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Workaround3.14.0S
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.1S
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.2S
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.3S
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.4S
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.0S
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.1S
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.1cS
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.2S
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.3S
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.4S
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.0S
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.0aS
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.0bS
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.0cS
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.1S
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.1aS
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.2S
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.2aS
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.2bS
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.3S
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.3aS
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.4S
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.4aS
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.4bS
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.4cS
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.4dS
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.4eS
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.4gS
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.5S
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.5aS
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.5bS
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.6S
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.0S
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.1S
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.1aS
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.2S
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.3S
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.0S
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.0aS
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.1S
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.2S
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.3S
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 IOS
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
Advisories wie diese benennen die exponierten Produkte, die Angreifer auf Ihrer Angriffsfläche ins Visier nehmen. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan