dbcve.org
JunosOperating system · Juniper

CVE-2019-0037

HIGH · 7.5 CVSS v3.1 Published 2019-04-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
In a Dynamic Host Configuration Protocol version 6 (DHCPv6) environment, the jdhcpd daemon may crash and restart upon receipt of certain DHCPv6 solicit messages received from a DHCPv6 client. By continuously sending the same crafted packet, an attacker can repeatedly crash the jdhcpd process causing a sustained Denial of Service (DoS) to both IPv4 and IPv6 clients. 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-D171, 15.1X49-D180; 15.1X53 versions prior to 15.1X53-D236, 15.1X53-D496; 16.1 versions prior to 16.1R3-S10, 16.1R7-S4; 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-S3; 18.1 versions prior to 18.1R2-S4, 18.1R3-S2; 18.2 versions prior to 18.2R2; 18.2X75 versions prior to 18.2X75-D30; 18.3 versions prior to 18.3R1-S2. This issue does not affect Junos OS releases prior to 15.1.

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 memory corruption or parsing error in the jdhcpd daemon causes a crash when processing specially crafted DHCPv6 solicit messages. An unauthenticated remote attacker can send these packets to trigger the crash, and by continuously resending the crafted packet, can maintain a sustained denial of service affecting both IPv4 and IPv6 DHCP clients.

MitigationApply the appropriate Junos OS version update listed in the advisory (e.g., 15.1F6-S12, 15.1X49-D171, 16.1R3-S10, etc.) or later. If immediate patching is not feasible, consider blocking DHCPv6 traffic from untrusted sources at network boundaries.

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= 15.1x49-d30= 15.1x49-d60= 15.1x49-d140= 15.1x49-d150= 15.1x49-d160= 15.1x53-d50= 15.1x53-d51= 15.1x53-d52= 15.1x53-d55= 15.1x53-d57= 15.1x53-d58

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.1/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 the Junos OS version
    Run 'show version' or 'show version detail' on the Juniper device CLI to obtain the installed Junos version
    Affected if The displayed version matches any of these exact versions: 15.1, 15.1X49-D30, 15.1X49-D60, 15.1X49-D140, 15.1X49-D150, 15.1X49-D160, 15.1X53-D50, 15.1X53-D51, 15.1X53-D52, 15.1X53-D55, 15.1X53-D57, or 15.1X53-D58
  2. Confirm jdhcpd daemon is running
    Run 'show system processes extensive | match jdhcpd' or check daemon status via 'show system services dhcp'
    Affected if The jdhcpd daemon is active and processing DHCP requests
  3. Verify DHCPv6 service is enabled
    Run 'show system services dhcpv6' to check if DHCPv6 service is configured
    Affected if DHCPv6 service is enabled and accepting solicit messages on the device
  4. Check for recent jdhcpd crash indicators
    Run 'show system core-dumps' and review system logs with 'show log messages | match jdhcpd' for crash or daemon restart entries
    Affected if Recent crashes or unexpected restarts of the jdhcpd daemon are logged and correlate with DHCPv6 traffic

You are affected if your Junos version exactly matches one of the 15.1 variants listed AND the jdhcpd daemon with DHCPv6 is running on your device.

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

Apply the appropriate Junos OS version update listed in the advisory (e.g., 15.1F6-S12, 15.1X49-D171, 16.1R3-S10, etc.) or later. If immediate patching is not feasible, consider blocking DHCPv6 traffic from untrusted sources at network boundaries.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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