First published: Fri Oct 04 2002(Updated: )
Cisco IOS 12.0 through 12.2, when supporting SSH, allows remote attackers to cause a denial of service (CPU consumption) via a large packet that was designed to exploit the SSH CRC32 attack detection overflow (CVE-2001-0144).
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Cisco CatOS | =6.1\(2.13\) | |
Cisco CatOS | =5.4\(4\) | |
Cisco CatOS | =5.5\(4\) | |
Cisco CatOS | =5.5\(13\) | |
Cisco CatOS | =7.1\(2\) | |
Cisco CatOS | =6.2\(0.110\) | |
Cisco CatOS | =6.2\(0.111\) | |
Cisco CatOS | =5.4\(1\) | |
Cisco CatOS | =5.5 | |
Cisco CatOS | =6.1\(1\) | |
Cisco CatOS | =5.5\(1\) | |
Cisco CatOS | =6.1\(1b\) | |
Cisco CatOS | =6.1\(1a\) | |
Cisco CatOS | =5.5\(4b\) | |
Cisco CatOS | =5.3\(5\)csx | |
Cisco CatOS | =5.3\(1a\)csx | |
Cisco CatOS | =5.3\(2\)csx | |
Cisco CatOS | =7.1 | |
Cisco CatOS | =5.3\(4\)csx | |
Cisco CatOS | =5.5\(4a\) | |
Cisco CatOS | =5.4\(3\) | |
Cisco CatOS | =6.3\(4\) | |
Cisco CatOS | =5.5\(3\) | |
Cisco CatOS | =5.3\(3\)csx | |
Cisco CatOS | =5.4 | |
Cisco CatOS | =5.3\(6\)csx | |
Cisco CatOS | =5.4\(2\) | |
Cisco CatOS | =6.3\(0.7\)pan | |
Cisco CatOS | =5.5\(2\) | |
Cisco CatOS | =5.3\(5a\)csx | |
Cisco CatOS | =5.3\(1\)csx | |
Cisco CatOS | =6.1\(1c\) | |
Puppet Cisco IOS | =12.0s | |
Puppet Cisco IOS | =12.0sp | |
Puppet Cisco IOS | =12.0st | |
Puppet Cisco IOS | =12.0xb | |
Puppet Cisco IOS | =12.0xm | |
Puppet Cisco IOS | =12.0xv | |
Puppet Cisco IOS | =12.1\(1\)ex | |
Puppet Cisco IOS | =12.1\(5c\)ex | |
Puppet Cisco IOS | =12.1\(8a\)ex | |
Puppet Cisco IOS | =12.1\(9\)ex | |
Puppet Cisco IOS | =12.1e | |
Puppet Cisco IOS | =12.1ec | |
Puppet Cisco IOS | =12.1t | |
Puppet Cisco IOS | =12.1xb | |
Puppet Cisco IOS | =12.1xc | |
Puppet Cisco IOS | =12.1xf | |
Puppet Cisco IOS | =12.1xg | |
Puppet Cisco IOS | =12.1xh | |
Puppet Cisco IOS | =12.1xi | |
Puppet Cisco IOS | =12.1xj | |
Puppet Cisco IOS | =12.1xl | |
Puppet Cisco IOS | =12.1xm | |
Puppet Cisco IOS | =12.1xp | |
Puppet Cisco IOS | =12.1xq | |
Puppet Cisco IOS | =12.1xt | |
Puppet Cisco IOS | =12.1xu | |
Puppet Cisco IOS | =12.1yb | |
Puppet Cisco IOS | =12.1yc | |
Puppet Cisco IOS | =12.1yd | |
Puppet Cisco IOS | =12.1ye | |
Puppet Cisco IOS | =12.1yf | |
Puppet Cisco IOS | =12.1yi | |
Puppet Cisco IOS | =12.2 | |
Puppet Cisco IOS | =12.2b | |
Puppet Cisco IOS | =12.2bc | |
Puppet Cisco IOS | =12.2da | |
Puppet Cisco IOS | =12.2dd | |
Puppet Cisco IOS | =12.2s | |
Puppet Cisco IOS | =12.2t | |
Puppet Cisco IOS | =12.2xa | |
Puppet Cisco IOS | =12.2xb | |
Puppet Cisco IOS | =12.2xd | |
Puppet Cisco IOS | =12.2xe | |
Puppet Cisco IOS | =12.2xf | |
Puppet Cisco IOS | =12.2xg | |
Puppet Cisco IOS | =12.2xh | |
Puppet Cisco IOS | =12.2xi | |
Puppet Cisco IOS | =12.2xj | |
Puppet Cisco IOS | =12.2xk | |
Puppet Cisco IOS | =12.2xl | |
Puppet Cisco IOS | =12.2xm | |
Puppet Cisco IOS | =12.2xn | |
Puppet Cisco IOS | =12.2xq | |
Puppet Cisco IOS | =12.2xr | |
Puppet Cisco IOS | =12.2xs | |
Puppet Cisco IOS | =12.2xt | |
Puppet Cisco IOS | =12.2xw | |
Puppet Cisco IOS | =12.2ya | |
Puppet Cisco IOS | =12.2yb | |
Puppet Cisco IOS | =12.2yc | |
Puppet Cisco IOS | =12.2yd | |
Puppet Cisco IOS | =12.2yf | |
Puppet Cisco IOS | =12.2yg | |
Puppet Cisco IOS | =12.2yh | |
Cisco PIX Firewall | =5.2 | |
Cisco PIX Firewall | =5.3 | |
Cisco PIX Firewall | =6.0 | |
Cisco PIX Firewall | =6.1 | |
Cisco PIX Firewall | =6.2 | |
Cisco Content Services Switch 11000 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2002-1024 has a severity rating of high due to its potential to cause denial of service by consuming CPU resources.
To mitigate CVE-2002-1024, upgrade to a Cisco IOS version that is not vulnerable, specifically versions later than 12.2.
CVE-2002-1024 affects various Cisco IOS versions, including 12.0 through 12.2, as well as certain Cisco CatOS and PIX Firewall versions.
The primary impact of CVE-2002-1024 is a denial of service condition, which can lead to network downtime and interruptions.
While the best solution is to update the affected systems, administrators can also implement access controls to limit exposure to the vulnerability.