# CVE-2018-0057: Business logic in Junos OS

> Malicious DHCP subscribers can bypass static IP bindings to cause duplicate assignments, leading to denial of service or information disclosure.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6ffm-w2x6-jcwh

## What is CVE-2018-0057?

CVE-2018-0057 is a medium-severity vulnerability in Juniper Junos, published on 10 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2018-0057?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2018-0057?

No fix has been published for CVE-2018-0057 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-0057 being exploited?

There is no known exploitation of CVE-2018-0057 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0057 and fix it if it is affected.

What it is: CVE-2018-0057 is a medium-severity vulnerability in Juniper Junos, published on 10 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0057 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-0057/ (Markdown: https://insights.sbomify.com/CVE-2018-0057/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-0057
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-0057
- OSV: https://osv.dev/vulnerability/CVE-2018-0057

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-0057/
Summaries are generated and may contain mistakes; the official description above is the record.