S-242: Vulnerability in Cisco IOS with OSPF, MPLS VPN, and Supervisor 32, Supervisor


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-242: Vulnerability in Cisco IOS with OSPF, MPLS VPN, and Supervisor 32, Supervisor
# 1  
Old 03-27-2008
S-242: Vulnerability in Cisco IOS with OSPF, MPLS VPN, and Supervisor 32, Supervisor

Cetrain Cisco Catalyst 6500 Series and Cisco 7600 Router devices that run branches of Cisco IOS based on 12.2 can be vulnerable to a denial of service vulnerability that can prevent any traffic from entering an affected interface. The risk is LOW. Exploitation of this vulnerability may result in a blocked interface input queue, memory leak, and/or restart of the device. Repeated exploitation of this vulnerability may result in an extended denial of service.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Solaris

Cisco IOS VPN server IKE

How do I tell if Cisco IOS VPN server IKE is running on my solaris 10 system (1 Reply)
Discussion started by: pgsanders
1 Replies

2. Shell Programming and Scripting

Need help on ssh login script to cisco ios

I'm trying to write a login script to ssh into a cisco switch that will run some command remotely. Similar to this expect script located here: SSH login expect shell script to supply username and password However, that script does not work with cisco ios. Anyway know what the best way to... (1 Reply)
Discussion started by: streetfighter2
1 Replies

3. Shell Programming and Scripting

continue after connecting to cisco vpn

Hi all, This will save me a tremendous amount of time if i can get this script working. I have alot of sites i need to connect to using cisco vpn and then ssh onto servers to retrieve some info. Its all repetitative and it needs scripted. what i have done so far is put this into a script. ... (0 Replies)
Discussion started by: borderblaster
0 Replies

4. IP Networking

Cisco vpn client

Who in the 64 ubuntu adopted cisco vpn client on the wireless network I downloaded the cisco vpn client for linux but run vpn_install make file when an error in cisco with the help of the document read in half a day, nor do I know this vpn client in the 64 systems in use. Who can help me, a... (1 Reply)
Discussion started by: Eason
1 Replies

5. UNIX for Dummies Questions & Answers

Patrol Supervisor can anyone help : /

Hello all Are you familiar with Patrol 3.5 software ? If so , I would like to know if in Patrol logs , we could find users' history ? Thank you (0 Replies)
Discussion started by: JuniorJack
0 Replies
Login or Register to Ask a Question
Info::Layer2::Catalyst(3pm)				User Contributed Perl Documentation			       Info::Layer2::Catalyst(3pm)

NAME
SNMP::Info::Layer2::Catalyst - SNMP Interface to Cisco Catalyst devices running Catalyst OS. AUTHOR
Max Baker SYNOPSIS
# Let SNMP::Info determine the correct subclass for you. my $cat = new SNMP::Info( AutoSpecify => 1, Debug => 1, DestHost => 'myswitch', Community => 'public', Version => 2 ) or die "Can't connect to DestHost. "; my $class = $cat->class(); print "SNMP::Info determined this device to fall under subclass : $class "; DESCRIPTION
SNMP::Info subclass to provide information for Cisco Catalyst series switches running CatOS. This class includes the Catalyst 2920, 4000, 5000, 6000 (hybrid mode) families. This subclass is not for all devices that have the name Catalyst. Note that some Catalyst switches run IOS, like the 2900 and 3550 families. Cisco Catalyst 1900 switches use their own MIB and have a separate subclass. Use the method above to have SNMP::Info determine the appropriate subclass before using this class directly. See SNMP::Info::device_type() for specifics. Note: Some older Catalyst switches will only talk SNMP version 1. Some newer ones will not return all their data if connected via Version 1. For speed or debugging purposes you can call the subclass directly, but not after determining a more specific class using the method above. my $cat = new SNMP::Info::Layer2::Catalyst(...); Inherited Classes SNMP::Info::CiscoStack SNMP::Info::CiscoVTP SNMP::Info::CDP SNMP::Info::CiscoStats SNMP::Info::CiscoPortSecurity SNMP::Info::Layer2 Required MIBs Inherited Classes' MIBs See "Required MIBs" in SNMP::Info::CiscoStack for its own MIB requirements. See "Required MIBs" in SNMP::Info::CiscoVTP for its own MIB requirements. See "Required MIBs" in SNMP::Info::CDP for its own MIB requirements. See "Required MIBs" in SNMP::Info::CiscoStats for its own MIB requirements. See "Required MIBs" in SNMP::Info::CiscoPortSecurity for its own MIB requirements. See "Required MIBs" in SNMP::Info::Layer2 for its own MIB requirements. These MIBs are found in the standard v2 MIBs from Cisco. GLOBALS
These are methods that return scalar value from SNMP $cat->os() Returns 'catalyst' $cat->os_ver() Tries to use the value from SNMP::Info::CiscoStats->os_ver() and if it fails it grabs $cat->m_swver()->{1} and uses that. $cat->vendor() Returns 'cisco' $cat->cisco_comm_indexing() Returns 1. Use vlan indexing. Global Methods imported from SNMP::Info::CiscoStack See documentation in "GLOBALS" in SNMP::Info::CiscoStack for details. Globals imported from SNMP::Info::CiscoVTP See documentation in "GLOBALS" in SNMP::Info::CiscoVTP for details. Global Methods imported from SNMP::Info::CDP See documentation in "GLOBALS" in SNMP::Info::CDP for details. Global Methods imported from SNMP::Info::CiscoStats See documentation in "GLOBALS" in SNMP::Info::CiscoStats for details. Global Methods imported from SNMP::Info::CiscoPortSecurity See documentation in "GLOBALS" in SNMP::Info::CiscoPortSecurity for details. Globals imported from SNMP::Info::Layer2 See documentation in "GLOBALS" in SNMP::Info::Layer2 for details. TABLE METHODS
These are methods that return tables of information in the form of a reference to a hash. Overrides $cat->interfaces() Returns the map between SNMP Interface Identifier (iid) and physical port name. $cat->i_name() Returns reference to hash of iid to human set name. "portName" $cat->i_physical() Returns a map to IID for ports that are physical ports, not vlans, etc. $cat->bp_index() Returns reference to hash of bridge port table entries map back to interface identifier (iid) Crosses ("portCrossIndex") to ("portIfIndex") since some devices seem to have problems with BRIDGE-MIB Table Methods imported from SNMP::Info::CiscoStack See documentation in "TABLE METHODS" in SNMP::Info::CiscoStack for details. Table Methods imported from SNMP::Info::CiscoVTP See documentation in "TABLE METHODS" in SNMP::Info::CiscoVTP for details. Table Methods imported from SNMP::Info::CDP See documentation in "TABLE METHODS" in SNMP::Info::CDP for details. Table Methods imported from SNMP::Info::CiscoStats See documentation in "TABLE METHODS" in SNMP::Info::CiscoStats for details. Table Methods imported from SNMP::Info::CiscoPortSecurity See documentation in "TABLE METHODS" in SNMP::Info::CiscoPortSecurity for details. Table Methods imported from SNMP::Info::Layer2 See documentation in "TABLE METHODS" in SNMP::Info::Layer2 for details. perl v5.12.4 2011-09-28 Info::Layer2::Catalyst(3pm)