CVE-2018-0057

Junos OS: authd allows assignment of IP address requested by DHCP subscriber logging in with Option 50 (Requested IP Address)

MEDIUM
6.1
CVSS Score
Published: October 10, 2018 at 06:00 PM UTC
Updated: June 17, 2026 at 01:29 AM UTC
1 product affected across 1 vendorJunos

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.1
Exploit prediction
EPSS 1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

15.1 ≤ v < 15.1R7-S2, 15.1R816.1 ≤ v < 16.1R4-S12, 16.1R7-S2, 16.1R816.2 ≤ v < 16.2R2-S7, 16.2R317.1 ≤ v < 17.1R2-S9, 17.1R317.2 ≤ v < 17.2R1-S7, 17.2R2-S6, 17.2R317.3 ≤ v < 17.3R2-S4, 17.3R317.4 ≤ v < 17.4R218.1 ≤ v < 18.1R2-S3, 18.1R315.115.1 f215.1 f315.1 f415.1 f515.1 f615.1 r115.1 r215.1 r315.1 r415.1 r515.1 r616.116.1 r116.1 r216.1 r316.216.2 r117.117.1 r117.217.317.3 r117.417.4 r118.118.1 r1
Affected range stops below 15.1R7-S2, 15.1R8, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.1R4-S12, 16.1R7-S2, 16.1R8, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.2R2-S7, 16.2R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.1R2-S9, 17.1R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.2R1-S7, 17.2R2-S6, 17.2R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.3R2-S4, 17.3R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.4R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.1R2-S3, 18.1R3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

x_refsource_CONFIRMVendor Advisory
https://kb.juniper.net/JSA10892

CVSS

6.1MEDIUMjuniper
Attack Vector
ADJACENT_NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
LOW
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card