dbcve.org
JunosOperating system · Juniper

CVE-2018-0062

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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
A Denial of Service vulnerability in J-Web service may allow a remote unauthenticated user to cause Denial of Service which may prevent other users to authenticate or to perform J-Web operations. Affected releases are Juniper Networks Junos OS: 12.1X46 versions prior to 12.1X46-D77 on SRX Series; 12.3 versions prior to 12.3R12-S10; 12.3X48 versions prior to 12.3X48-D60 on SRX Series; 15.1 versions prior to 15.1R7; 15.1F6; 15.1X49 versions prior to 15.1X49-D120 on SRX Series; 15.1X53 versions prior to 15.1X53-D59 on EX2300/EX3400 Series; 15.1X53 versions prior to 15.1X53-D67 on QFX10K Series; 15.1X53 versions prior to 15.1X53-D234 on QFX5200/QFX5110 Series; 15.1X53 versions prior to 15.1X53-D470, 15.1X53-D495 on NFX Series; 16.1 versions prior to 16.1R6; 16.2 versions prior to 16.2R2-S6, 16.2R3; 17.1 versions prior to 17.1R2-S6, 17.1R3; 17.2 versions prior to 17.2R3; 17.3 versions prior to 17.3R2. No other Juniper Networks products or platforms are affected by this issue.

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

A remote unauthenticated attacker can exploit a flaw in the J-Web service component of Juniper Junos OS to cause a Denial of Service condition. The vulnerability prevents legitimate users from authenticating to J-Web or performing J-Web operations, effectively locking out administrative access.

MitigationUpgrade Junos OS to the patched versions specified (12.1X46-D77, 12.3R12-S10, 12.3X48-D60, 15.1R7, 15.1X49-D120, 15.1X53-D59/D67/D234/D470/D495, 16.1R6, 16.2R3, 17.1R3, 17.2R3, 17.3R2) or disable J-Web service if not required.

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:= 12.1x46= 12.3= 12.3x48= 15.1= 15.1x49= 15.1x53= 16.1= 16.2= 17.1= 17.2= 17.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Junos OS version
    Run 'show version' command on the device CLI to obtain the Junos OS version number
    Affected if The version falls within these affected branches: 12.1X46, 12.3, 12.3X48, 15.1, 15.1X49, 15.1X53, 16.1, 16.2, 17.1, 17.2, or 17.3 (including all point releases within these series)
  2. Verify J-Web service is exposed
    Check if J-Web interface is accessible by attempting to reach the device on port 443 (HTTPS) or port 8443, or run 'show system services web-management' to confirm J-Web is enabled
    Affected if J-Web service is enabled and reachable on the network (the vulnerability only affects systems with J-Web exposed)
  3. Confirm J-Web is not the httpd process
    Run 'show system processes | match httpd' to verify J-Web daemon (jweb) is running, or check 'show system services web-management http' to see J-Web configuration status
    Affected if J-Web daemon process is active on the device

You are affected if your Junos OS version is in the 12.1X46, 12.3, 12.3X48, 15.1, 15.1X49, 15.1X53, 16.1, 16.2, 17.1, 17.2, or 17.3 series AND J-Web service is enabled and accessible on your network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to the patched versions specified (12.1X46-D77, 12.3R12-S10, 12.3X48-D60, 15.1R7, 15.1X49-D120, 15.1X53-D59/D67/D234/D470/D495, 16.1R6, 16.2R3, 17.1R3, 17.2R3, 17.3R2) or disable J-Web service if not required.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0062 — 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-0062 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