# CVE-2019-0037: Junos OS: jdhcpd crash upon receipt of crafted DHCPv6 solicit message

> An attacker can cause a sustained denial of service by repeatedly sending crafted DHCPv6 solicit messages to crash the jdhcpd daemon.

- **Severity:** High 7.4 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **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 Apr 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g767-h356-7hx2

## What is CVE-2019-0037?

CVE-2019-0037 is a high-severity denial of service vulnerability in Juniper Junos, published on 10 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2019-0037?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2019-0037?

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

## Is CVE-2019-0037 being exploited?

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

What it is: CVE-2019-0037 is a high-severity denial of service vulnerability in Juniper Junos, published on 10 Apr 2019. 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-2019-0037 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-2019-0037/ (Markdown: https://insights.sbomify.com/CVE-2019-0037/index.md)
```

## Sources

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

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