The NTP implementation in Cisco IOS 12.0 through 12.4 and 15.0 through 15.1, and IOS XE 2.1 through 3.3, does not properly handle encapsulation of multicast NTP packets within MSDP SA messages, which allows remote attackers to cause a denial of service (device reload) by leveraging an MSDP peer relationship, aka Bug ID CSCuc81226.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Ios_xe | Cisco | 2.1.0 (including) | 2.1.0 (including) |
Ios_xe | Cisco | 2.1.1 (including) | 2.1.1 (including) |
Ios_xe | Cisco | 2.1.2 (including) | 2.1.2 (including) |
Ios_xe | Cisco | 2.2.1 (including) | 2.2.1 (including) |
Ios_xe | Cisco | 2.2.2 (including) | 2.2.2 (including) |
Ios_xe | Cisco | 2.2.3 (including) | 2.2.3 (including) |
Ios_xe | Cisco | 2.3.0 (including) | 2.3.0 (including) |
Ios_xe | Cisco | 2.3.1 (including) | 2.3.1 (including) |
Ios_xe | Cisco | 2.3.1t (including) | 2.3.1t (including) |
Ios_xe | Cisco | 2.3.2 (including) | 2.3.2 (including) |
Ios_xe | Cisco | 2.4.0 (including) | 2.4.0 (including) |
Ios_xe | Cisco | 2.4.1 (including) | 2.4.1 (including) |
Ios_xe | Cisco | 2.4.2 (including) | 2.4.2 (including) |
Ios_xe | Cisco | 2.4.3 (including) | 2.4.3 (including) |
Ios_xe | Cisco | 2.4.4 (including) | 2.4.4 (including) |
Ios_xe | Cisco | 2.5.0 (including) | 2.5.0 (including) |
Ios_xe | Cisco | 2.5.1 (including) | 2.5.1 (including) |
Ios_xe | Cisco | 2.5.2 (including) | 2.5.2 (including) |
Ios_xe | Cisco | 2.6.0 (including) | 2.6.0 (including) |
Ios_xe | Cisco | 2.6.1 (including) | 2.6.1 (including) |
Ios_xe | Cisco | 2.6.2 (including) | 2.6.2 (including) |
Ios_xe | Cisco | 3.1.0s (including) | 3.1.0s (including) |
Ios_xe | Cisco | 3.1.0sg (including) | 3.1.0sg (including) |
Ios_xe | Cisco | 3.1.1s (including) | 3.1.1s (including) |
Ios_xe | Cisco | 3.1.1sg (including) | 3.1.1sg (including) |
Ios_xe | Cisco | 3.1.2s (including) | 3.1.2s (including) |
Ios_xe | Cisco | 3.1.3s (including) | 3.1.3s (including) |
Ios_xe | Cisco | 3.1.4s (including) | 3.1.4s (including) |
Ios_xe | Cisco | 3.2.00.xo.15.0(2)xo (including) | 3.2.00.xo.15.0(2)xo (including) |
Ios_xe | Cisco | 3.2.0s (including) | 3.2.0s (including) |
Ios_xe | Cisco | 3.2.0sg (including) | 3.2.0sg (including) |
Ios_xe | Cisco | 3.2.0xo (including) | 3.2.0xo (including) |
Ios_xe | Cisco | 3.2.1s (including) | 3.2.1s (including) |
Ios_xe | Cisco | 3.2.1sg (including) | 3.2.1sg (including) |
Ios_xe | Cisco | 3.2.2s (including) | 3.2.2s (including) |
Ios_xe | Cisco | 3.2.2sg (including) | 3.2.2sg (including) |
Ios_xe | Cisco | 3.2.3sg (including) | 3.2.3sg (including) |
Ios_xe | Cisco | 3.2.4sg (including) | 3.2.4sg (including) |
Ios_xe | Cisco | 3.3.0s (including) | 3.3.0s (including) |
Ios_xe | Cisco | 3.3.0sg (including) | 3.3.0sg (including) |
Input validation is a frequently-used technique for checking potentially dangerous inputs in order to ensure that the inputs are safe for processing within the code, or when communicating with other components. Input can consist of:
Data can be simple or structured. Structured data can be composed of many nested layers, composed of combinations of metadata and raw data, with other simple or structured data. Many properties of raw data or metadata may need to be validated upon entry into the code, such as:
Implied or derived properties of data must often be calculated or inferred by the code itself. Errors in deriving properties may be considered a contributing factor to improper input validation.