# CVE-2018-0035: Junos OS: QFX5200 and QFX10002: Unintended ONIE partition was shipped with certain Junos OS .bin and .iso images

> Attackers can gain root access via an unintended ONIE partition on specific Juniper switches, allowing them to wipe configurations and bypass authentication.

- **Severity:** Medium 4.4 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g949-ppgf-vg49

## What is CVE-2018-0035?

CVE-2018-0035 is a medium-severity authentication bypass vulnerability in Juniper Junos, published on 11 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

QFX5200 and QFX10002 devices that have been shipped with Junos OS 15.1X53-D21, 15.1X53-D30, 15.1X53-D31, 15.1X53-D32, 15.1X53-D33 and 15.1X53-D60 or have been upgraded to these releases using the .bin or .iso images may contain an unintended additional Open Network Install Environment (ONIE) partition. This additional partition allows the superuser to reboot to the ONIE partition which will wipe out the content of the Junos partition and its configuration. Once rebooted, the ONIE partition will not have root password configured, thus any user can access the console or SSH, using an IP address acquired from DHCP, as root without password. Once the device has been shipped or upgraded with the ONIE partition installed, the issue will persist. Simply upgrading to higher release via the CLI will not resolve the issue. No other Juniper Networks products or platforms are affected by this issue.

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2018-0035 being exploited?

There is no known exploitation of CVE-2018-0035 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-0035 and fix it if it is affected.

What it is: CVE-2018-0035 is a medium-severity authentication bypass vulnerability in Juniper Junos, published on 11 Jul 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-0035 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-0035/ (Markdown: https://insights.sbomify.com/CVE-2018-0035/index.md)
```

## Sources

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

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