An Improper Validation of Syntactic Correctness of Input vulnerability in the kernel of Juniper Networks Junos OS Evolved on PTX series allows a network-based, unauthenticated attacker to cause a Denial of Service (DoS). When an incoming TCP packet destined to the device is malformed there is a possibility of a kernel panic. Only TCP packets destined to the ports for BGP, LDP and MSDP can trigger this. This issue only affects PTX10004, PTX10008, PTX10016. No other PTX Series devices or other platforms are affected. This issue affects Juniper Networks Junos OS Evolved: 20.4-EVO versions prior to 20.4R3-S4-EVO; 21.3-EVO versions prior to 21.3R3-EVO; 21.4-EVO versions prior to 21.4R3-EVO; 22.1-EVO versions prior to 22.1R2-EVO. This issue does not affect Juniper Networks Junos OS Evolved versions prior to 20.4R1-EVO.
The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Junos_os_evolved | Juniper | 20.4-r1 (including) | 20.4-r1 (including) |
Junos_os_evolved | Juniper | 20.4-r1-s1 (including) | 20.4-r1-s1 (including) |
Junos_os_evolved | Juniper | 20.4-r1-s2 (including) | 20.4-r1-s2 (including) |
Junos_os_evolved | Juniper | 20.4-r2 (including) | 20.4-r2 (including) |
Junos_os_evolved | Juniper | 20.4-r2-s1 (including) | 20.4-r2-s1 (including) |
Junos_os_evolved | Juniper | 20.4-r2-s2 (including) | 20.4-r2-s2 (including) |
Junos_os_evolved | Juniper | 20.4-r2-s3 (including) | 20.4-r2-s3 (including) |
Junos_os_evolved | Juniper | 20.4-r3 (including) | 20.4-r3 (including) |
Junos_os_evolved | Juniper | 20.4-r3-s1 (including) | 20.4-r3-s1 (including) |
Junos_os_evolved | Juniper | 20.4-r3-s2 (including) | 20.4-r3-s2 (including) |
Junos_os_evolved | Juniper | 20.4-r3-s3 (including) | 20.4-r3-s3 (including) |
Junos_os_evolved | Juniper | 21.3-r1 (including) | 21.3-r1 (including) |
Junos_os_evolved | Juniper | 21.3-r1-s1 (including) | 21.3-r1-s1 (including) |
Junos_os_evolved | Juniper | 21.3-r2 (including) | 21.3-r2 (including) |
Junos_os_evolved | Juniper | 21.3-r2-s1 (including) | 21.3-r2-s1 (including) |
Junos_os_evolved | Juniper | 21.3-r2-s2 (including) | 21.3-r2-s2 (including) |
Junos_os_evolved | Juniper | 21.4 (including) | 21.4 (including) |
Junos_os_evolved | Juniper | 21.4-r1 (including) | 21.4-r1 (including) |
Junos_os_evolved | Juniper | 21.4-r1-s1 (including) | 21.4-r1-s1 (including) |
Junos_os_evolved | Juniper | 21.4-r2 (including) | 21.4-r2 (including) |
Junos_os_evolved | Juniper | 21.4-r2-s1 (including) | 21.4-r2-s1 (including) |
Junos_os_evolved | Juniper | 21.4-r2-s2 (including) | 21.4-r2-s2 (including) |
Junos_os_evolved | Juniper | 22.1-r1 (including) | 22.1-r1 (including) |
Junos_os_evolved | Juniper | 22.1-r1-s1 (including) | 22.1-r1-s1 (including) |
Junos_os_evolved | Juniper | 22.1-r1-s2 (including) | 22.1-r1-s2 (including) |
Often, complex inputs are expected to follow a particular syntax, which is either assumed by the input itself, or declared within metadata such as headers. The syntax could be for data exchange formats, markup languages, or even programming languages. When untrusted input is not properly validated for the expected syntax, attackers could cause parsing failures, trigger unexpected errors, or expose latent vulnerabilities that might not be directly exploitable if the input had conformed to the syntax.