# CVE-2019-0002: Junos OS: EX2300 and EX3400 series: Certain stateless firewall filter rules might not take effect

> Attackers can bypass stateless firewall filters on Juniper EX2300/EX3400 switches when specific policer actions are configured, potentially allowing unauthorized traffic.

- **Severity:** Medium 5.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **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:** 16 Sep 2024
- **Also known as:** GHSA-9v62-432v-6vc6

## What is CVE-2019-0002?

CVE-2019-0002 is a medium-severity 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

On EX2300 and EX3400 series, stateless firewall filter configuration that uses the action 'policer' in combination with other actions might not take effect. When this issue occurs, the output of the command: show pfe filter hw summary will not show the entry for: RACL group Affected releases are Junos OS on EX2300 and EX3400 series: 15.1X53 versions prior to 15.1X53-D590; 18.1 versions prior to 18.1R3; 18.2 versions prior to 18.2R2. This issue affect both IPv4 and IPv6 firewall filter.

Weakness: CWE-794 (Incomplete Filtering of Multiple Instances of Special Elements)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2019-0002 being exploited?

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

What it is: CVE-2019-0002 is a medium-severity 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-0002 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-0002/ (Markdown: https://insights.sbomify.com/CVE-2019-0002/index.md)
```

## Sources

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

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