On EX4300 Series switches with TCAM optimization enabled, incoming multicast traffic matches an implicit loopback filter rule first, since it has high priority. This rule is meant for reserved multicast addresses 224.0.0.x, but incorrectly matches on 224.x.x.x. Due to this bug, when a firewall filter is applied on the loopback interface, other firewall filters might stop working for multicast traffic. The command show firewall filter can be used to confirm whether the filter is working. This issue only affects the EX4300 switch. No other products or platforms are affected by this vulnerability. This issue affects: Juniper Networks Junos OS: 14.1X53 versions prior to 14.1X53-D51, 14.1X53-D115 on EX4300 Series; 17.1 versions prior to 17.1R3 on EX4300 Series; 17.2 versions prior to 17.2R3-S2 on EX4300 Series; 17.3 versions prior to 17.3R3-S3 on EX4300 Series; 17.4 versions prior to 17.4R2-S5, 17.4R3 on EX4300 Series; 18.1 versions prior to 18.1R3-S1 on EX4300 Series; 18.2 versions prior to 18.2R2 on EX4300 Series; 18.3 versions prior to 18.3R2 on EX4300 Series.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Junos | Juniper | 14.1x53 (including) | 14.1x53 (including) |
| Junos | Juniper | 14.1x53-d10 (including) | 14.1x53-d10 (including) |
| Junos | Juniper | 14.1x53-d15 (including) | 14.1x53-d15 (including) |
| Junos | Juniper | 14.1x53-d16 (including) | 14.1x53-d16 (including) |
| Junos | Juniper | 14.1x53-d25 (including) | 14.1x53-d25 (including) |
| Junos | Juniper | 14.1x53-d26 (including) | 14.1x53-d26 (including) |
| Junos | Juniper | 14.1x53-d27 (including) | 14.1x53-d27 (including) |
| Junos | Juniper | 14.1x53-d30 (including) | 14.1x53-d30 (including) |
| Junos | Juniper | 14.1x53-d35 (including) | 14.1x53-d35 (including) |
| Junos | Juniper | 14.1x53-d40 (including) | 14.1x53-d40 (including) |
| Junos | Juniper | 14.1x53-d45 (including) | 14.1x53-d45 (including) |
| Junos | Juniper | 14.1x53-d48 (including) | 14.1x53-d48 (including) |
| Junos | Juniper | 14.1x53-d49 (including) | 14.1x53-d49 (including) |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.