On Junos OS, rpcbind should only be listening to port 111 on the internal routing instance (IRI). External packets destined to port 111 should be dropped. Due to an information leak vulnerability, responses were being generated from the source address of the management interface (e.g. fxp0) thus disclosing internal addressing and existence of the management interface itself. A high rate of crafted packets destined to port 111 may also lead to a partial Denial of Service (DoS). Note: Systems with fxp0 disabled or unconfigured are not vulnerable to this issue. This issue only affects Junos OS releases based on FreeBSD 10 or higher (typically Junos OS 15.1+). Administrators can confirm whether systems are running a version of Junos OS based on FreeBSD 10 or higher by typing: user@junos> show version | match kernel JUNOS OS Kernel 64-bit [20181214.223829_fbsd-builder_stable_10] Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1F6-S12, 15.1R7-S4; 15.1X53 versions prior to 15.1X53-D236; 16.1 versions prior to 16.1R7-S1; 16.2 versions prior to 16.2R2-S9; 17.1 versions prior to 17.1R3; 17.2 versions prior to 17.2R1-S8; 17.3 versions prior to 17.3R2; 17.4 versions prior to 17.4R1-S1, 17.4R1-S7, 17.4R2. This issue does not affect Junos OS releases prior to 15.1.
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 | 15.1 (including) | 15.1 (including) |
| Junos | Juniper | 15.1-a1 (including) | 15.1-a1 (including) |
| Junos | Juniper | 15.1-f1 (including) | 15.1-f1 (including) |
| Junos | Juniper | 15.1-f2 (including) | 15.1-f2 (including) |
| Junos | Juniper | 15.1-f2-s1 (including) | 15.1-f2-s1 (including) |
| Junos | Juniper | 15.1-f2-s2 (including) | 15.1-f2-s2 (including) |
| Junos | Juniper | 15.1-f2-s3 (including) | 15.1-f2-s3 (including) |
| Junos | Juniper | 15.1-f2-s4 (including) | 15.1-f2-s4 (including) |
| Junos | Juniper | 15.1-f3 (including) | 15.1-f3 (including) |
| Junos | Juniper | 15.1-f4 (including) | 15.1-f4 (including) |
| Junos | Juniper | 15.1-f5 (including) | 15.1-f5 (including) |
| Junos | Juniper | 15.1-f6 (including) | 15.1-f6 (including) |
| Junos | Juniper | 15.1-r1 (including) | 15.1-r1 (including) |
| Junos | Juniper | 15.1-r2 (including) | 15.1-r2 (including) |
| Junos | Juniper | 15.1-r3 (including) | 15.1-r3 (including) |
| Junos | Juniper | 15.1-r4 (including) | 15.1-r4 (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.