# CVE-2019-0003: Denial of service in Junos OS

> A reachable assertion failure in Junos OS causes the routing protocol daemon to crash when processing specific BGP flowspec updates, requiring a software upgrade.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3jqv-j83m-6qhf

## What is CVE-2019-0003?

CVE-2019-0003 is a high-severity denial of service vulnerability in Juniper Junos, published on 15 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When a specific BGP flowspec configuration is enabled and upon receipt of a specific matching BGP packet meeting a specific term in the flowspec configuration, a reachable assertion failure occurs, causing the routing protocol daemon (rpd) process to crash with a core file being generated. 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-D70 on SRX Series; 14.1X53 versions prior to 14.1X53-D47 on EX2200/VC, EX3200, EX3300/VC, EX4200, EX4300, EX4550/VC, EX4600, EX6200, EX8200/VC (XRE), QFX3500, QFX3600, QFX5100; 15.1 versions prior to 15.1R3; 15.1F versions prior to 15.1F3; 15.1X49 versions prior to 15.1X49-D140 on SRX Series; 15.1X53 versions prior to 15.1X53-D59 on EX2300/EX3400.

Weakness: CWE-617 (Reachable Assertion)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2019-0003 being exploited?

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

What it is: CVE-2019-0003 is a high-severity denial of service vulnerability in Juniper Junos, published on 15 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0003 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-0003/ (Markdown: https://insights.sbomify.com/CVE-2019-0003/index.md)
```

## Sources

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

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