On MX Series and M120/M320 platforms configured in a Broadband Edge (BBE) environment, subscribers logging in with DHCP Option 50 to request a specific IP address will be assigned the requested IP address, even if there is a static MAC to IP address binding in the access profile. In the problem scenario, with a hardware-address and IP address configured under address-assignment pool, if a subscriber logging in with DHCP Option 50, the subscriber will not be assigned an available address from the matched pool, but will still get the requested IP address. A malicious DHCP subscriber may be able to utilize this vulnerability to create duplicate IP address assignments, leading to a denial of service for valid subscribers or unauthorized information disclosure via IP address assignment spoofing. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1R7-S2, 15.1R8; 16.1 versions prior to 16.1R4-S12, 16.1R7-S2, 16.1R8; 16.2 versions prior to 16.2R2-S7, 16.2R3; 17.1 versions prior to 17.1R2-S9, 17.1R3; 17.2 versions prior to 17.2R1-S7, 17.2R2-S6, 17.2R3; 17.3 versions prior to 17.3R2-S4, 17.3R3; 17.4 versions prior to 17.4R2; 18.1 versions prior to 18.1R2-S3, 18.1R3.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 6.1, indicating it requires adjacent network access with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts limited data confidentiality, and limited availability for affected systems. Impacting 1 product from juniper organizations running these solutions should prioritize assessment and patching.
First disclosed in 2018, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2018-10-10T18:29:02.983
2024-11-21T03:37:28.720
Modified
CVSSv3.0: 6.1 (MEDIUM)
AV:N/AC:L/Au:S/C:P/I:N/A:P
8.0
4.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 15.1 | Yes |
| Operating System | juniper | junos | 16.1 | Yes |
| Operating System | juniper | junos | 16.1 | Yes |
| Operating System | juniper | junos | 16.1 | Yes |
| Operating System | juniper | junos | 16.1 | Yes |
| Operating System | juniper | junos | 16.2 | Yes |
| Operating System | juniper | junos | 16.2 | Yes |
| Operating System | juniper | junos | 17.1 | Yes |
| Operating System | juniper | junos | 17.1 | Yes |
| Operating System | juniper | junos | 17.2 | Yes |
| Operating System | juniper | junos | 17.3 | Yes |
| Operating System | juniper | junos | 17.3 | Yes |
| Operating System | juniper | junos | 17.4 | Yes |
| Operating System | juniper | junos | 17.4 | Yes |
| Operating System | juniper | junos | 18.1 | Yes |
| Operating System | juniper | junos | 18.1 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For juniper's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.