An Improper Validation of Specified Type of Input vulnerability in the kernel of Juniper Networks Junos OS allows an unauthenticated adjacent attacker to trigger a Missing Release of Memory after Effective Lifetime vulnerability. Continued exploitation of this vulnerability will eventually lead to an FPC reboot and thereby a Denial of Service (DoS). This issue affects: Juniper Networks Junos OS on vMX and MX150: All versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S5; 19.4 versions prior to 19.4R2-S5, 19.4R3-S6; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2-S1, 21.1R3; 21.2 versions prior to 21.2R1-S1, 21.2R2; 21.3 versions prior to 21.3R1-S1, 21.3R2.
The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Junos | Juniper | * | 19.1 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.2 | 19.2 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.3 | 19.3 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 19.4 | 19.4 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.1 | 20.1 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.2 | 20.2 |
Junos | Juniper | 20.3 | 20.3 |
Junos | Juniper | 20.3 | 20.3 |
Junos | Juniper | 20.3 | 20.3 |
Junos | Juniper | 20.3 | 20.3 |
Junos | Juniper | 20.3 | 20.3 |
Junos | Juniper | 20.4 | 20.4 |
Junos | Juniper | 20.4 | 20.4 |
Junos | Juniper | 20.4 | 20.4 |
Junos | Juniper | 20.4 | 20.4 |
Junos | Juniper | 21.1 | 21.1 |
Junos | Juniper | 21.1 | 21.1 |
Junos | Juniper | 21.1 | 21.1 |
Junos | Juniper | 21.2 | 21.2 |
Junos | Juniper | 21.3 | 21.3 |
When input does not comply with the expected type, attackers could trigger unexpected errors, cause incorrect actions to take place, or exploit latent vulnerabilities that would not be possible if the input conformed with the expected type. This weakness can appear in type-unsafe programming languages, or in programming languages that support casting or conversion of an input to another type.