An Improper Validation of Syntactic Correctness of Input vulnerability in the Web-Filtering module of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS).
If an SRX device configured for UTM Web-Filtering receives a specifically malformed SSL packet, this will cause an FPC crash and restart. This issue affects Junos OS on SRX Series:
- 23.2 versions from 23.2R2-S2 before 23.2R2-S5,
- 23.4 versions from 23.4R2-S1 before 23.4R2-S5,
- 24.2 versions before 24.2R2-S2,
- 24.4 versions before 24.4R1-S3, 24.4R2.
Earlier versions of Junos are also affected, but no fix is available.
Weakness
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.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Junos | Juniper | 23.2-r2-s2 (including) | 23.2-r2-s2 (including) |
| Junos | Juniper | 23.2-r2-s3 (including) | 23.2-r2-s3 (including) |
| Junos | Juniper | 23.2-r2-s4 (including) | 23.2-r2-s4 (including) |
| Junos | Juniper | 23.4-r2-s1 (including) | 23.4-r2-s1 (including) |
| Junos | Juniper | 23.4-r2-s2 (including) | 23.4-r2-s2 (including) |
| Junos | Juniper | 23.4-r2-s3 (including) | 23.4-r2-s3 (including) |
| Junos | Juniper | 23.4-r2-s4 (including) | 23.4-r2-s4 (including) |
| Junos | Juniper | 24.2 (including) | 24.2 (including) |
| Junos | Juniper | 24.2-r1 (including) | 24.2-r1 (including) |
| Junos | Juniper | 24.2-r1-s1 (including) | 24.2-r1-s1 (including) |
| Junos | Juniper | 24.2-r1-s2 (including) | 24.2-r1-s2 (including) |
| Junos | Juniper | 24.2-r2 (including) | 24.2-r2 (including) |
| Junos | Juniper | 24.2-r2-s1 (including) | 24.2-r2-s1 (including) |
| Junos | Juniper | 24.4 (including) | 24.4 (including) |
| Junos | Juniper | 24.4-r1 (including) | 24.4-r1 (including) |
| Junos | Juniper | 24.4-r1-s2 (including) | 24.4-r1-s2 (including) |
| Junos | Juniper | 24.4-r2 (including) | 24.4-r2 (including) |
Extended Description
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.
Potential Mitigations
- Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.