Specifications
1156
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S1
• CSCee65066
Symptoms: The CISCO-PIM-MIB trap ciscoPimInvalidJoinPrune is supposed to contain the
following varbinds:
1.3.6.1.4.1.9.9.184.1.1.4 - cpimLastErrorOriginType 1.3.6.1.4.1.9.9.184.1.1.5 -
1.3.6.1.4.1.9.9.184.1.1.4 - cpimLastErrorOriginType
1.3.6.1.4.1.9.9.184.1.1.5 - cpimLastErrorOrigin
1.3.6.1.4.1.9.9.184.1.1.6 - cpimLastErrorGroupType
1.3.6.1.4.1.9.9.184.1.1.7 - cpimLastErrorGroup
1.3.6.1.4.1.9.9.184.1.1.8 - cpimLastErrorRPType
1.3.6.1.4.1.9.9.184.1.1.9 - cpimLastErrorRP
1.3.6.1.4.1.9.9.184.1.1.2 - cpimInvalidJoinPruneMsgsRcvd
However, when the trap is sent, a wrong OID is used for the cpimInvalidJoinPruneMsgsRcvd.
From a sniffer trace, the following varbind is seen: 1.3.6.1.4.1.9.9.184.2.0.5.0. The actual value sent
is correct, though.
Similarly, another CISCO-PIM-MIB trap, ciscoPimInvalidRegister, has the wrong varbind for
cpimInvalidRegisterMsgsRcvd. However the value sent is correct in this case too.
Conditions: This symptom is platform-independent and software-independent. Note that the actual
value that is sent in the wrong OID for cpimInvalidJoinPruneMsgsRcvd or
cpimInvalidRegisterMsgsRcvd is correct. However, this situation causes confusion on the traps
receiver side because the receiver cannot decode the traps correctly.
Workaround: There is no workaround.
• CSCee67450
A Cisco device running Cisco IOS and enabled for the Border Gateway Protocol (BGP) is
vulnerable to a Denial of Service (DoS) attack from a malformed BGP packet. Only devices with
the bgp log-neighbor-changes command configured are vulnerable. The BGP protocol is not
enabled by default, and must be configured in order to accept traffic from an explicitly defined peer.
Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be
difficult to inject a malformed packet.
If a misformed packet is received and queued up on the interface, this bug may also be triggered by
other means which are not considered remotely exploitable such as the use of the show ip bgp
neighbors command or running the debug ip bgp neighbor updates command for a configured
BGP neighbor.
Cisco has made free software available to address this problem.
For more details, please refer to this advisory, available at
http://www.cisco.com/warp/public/707/cisco-sa-20050126-bgp.shtml
• CSCee69396
Symptoms: A Cisco 10000 series router that is running Cisco IOS Release 12.0(25)SX6 notices a
large increase of at least 15% in the CPU usage in the “BGP Router” process when upgraded from
Cisco IOS Release 12.0(23)SX5. This occurs under certain conditions where there are a very large
number of BGP neighbors in a PE-CE scenario. During the steady state after BGP router
convergence, there needs to be a constant churn in the updates with addition/withdrawal of the routes
from the neighbor BGP peers.
Conditions: This symptom is observed on a Cisco 10000 series router that is running Cisco IOS
Release 12.0(25)SX6. All versions starting from Cisco IOS Release 12.0(25)SX to
Release 12.0(25)SX6 are affected by this problem.