dbcve.org
JunosOperating system · Juniper

CVE-2018-0057

CRITICAL · 9.6 CVSS v3.0 Published 2018-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

On Juniper MX Series and M120/M320 platforms in BBE environments, DHCP Option 50 requests bypass static MAC-to-IP address bindings in access profiles, allowing subscribers to obtain any requested IP address regardless of configured bindings. This enables duplicate IP assignments, causing DoS for legitimate subscribers and potential information disclosure through IP spoofing.

MitigationUpgrade Junos OS to a patched version (15.1R7-S2 or later, 16.1R4-S12/16.1R7-S2/16.1R8 or later, etc.) as specified in the Juniper advisory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:= 15.1= 16.1= 16.2= 17.1= 17.2= 17.3= 17.4= 18.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Run 'show chassis hardware' or check the device model. Confirm it is a Juniper MX Series, M120, or M320 router.
    Affected if Device is an MX Series, M120, or M320 platform
  2. Check the Junos OS version
    Run 'show version' or 'show system information' to obtain the installed Junos version.
    Affected if Version is 15.1, 16.1, 16.2, 17.1, 17.2, 17.3, 17.4, or 18.1 (any build within these release trains)
  3. Confirm BBE environment is configured
    Run 'show configuration' and look for BBE-related configurations such as 'system services subscriber-management' or check for broadband edge services under 'access' or 'protocols' hierarchies.
    Affected if BBE (Broadband Edge) services are enabled on the device
  4. Verify DHCP is configured with static MAC-to-IP bindings
    Run 'show configuration access profile' and inspect for 'static-ip' entries under the DHCP pseudowire or subscriber interface configuration. Use 'show configuration | display set | match static-ip' to search for static bindings.
    Affected if DHCP access profiles contain static MAC-to-IP address bindings configured

All four conditions must be true for the device to be affected: MX/M120/M320 hardware, affected Junos version, BBE environment active, and DHCP with static MAC-to-IP bindings in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to a patched version (15.1R7-S2 or later, 16.1R4-S12/16.1R7-S2/16.1R8 or later, etc.) as specified in the Juniper advisory.

Recommended fix High confidence

Upgrade to the fixed release for your branch: 15.1R7-S2/15.1R8, 16.1R4-S12/16.1R7-S2/16.1R8, 16.2R2-S7/16.2R3, or 17.1R2-S9/17.1R3 (or later stable releases)

  1. 1. Identify the current Junos OS version running on the MX Series, M120, or M320 device using 'show version'
  2. 2. Determine the appropriate fixed release based on the current installed version: For 15.1 branch, upgrade to 15.1R7-S2 or 15.1R8; For 16.1 branch, upgrade to 16.1R4-S12, 16.1R7-S2, or 16.1R8; For 16.2 branch, upgrade to 16.2R2-S7 or 16.2R3; For 17.1 branch, upgrade to 17.1R2-S9 or 17.1R3
  3. 3. Download the appropriate Junos OS upgrade image from the Juniper Networks website (kb.juniper.net)
  4. 4. Back up the current configuration using 'request system configuration backup'
  5. 5. Upload the upgrade image to the device using FTP or SCP
  6. 6. Install the upgrade using 'request system software add <package-name>' and reboot the system
  7. 7. After reboot, verify the new Junos version with 'show version'
  8. 8. Verify the fix is applied by testing DHCP subscriber login with Option 50 to ensure static MAC-to-IP bindings are properly enforced
Caveat Review Juniper release notes for any changes to DHCP BBE behavior; test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0057 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-0057 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data