CVE-2019-0002 [Critical] | Security Vulnerability in Junos

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.23%	2.38%	+2.15%
2	2026-04-14	0.29%	0.23%	-0.06%
3	2025-10-04	—	0.29%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.23%

2.38%

+2.15%

2026-04-14

0.29%

0.23%

-0.06%

2025-10-04

—

0.29%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.9	[email protected]
5.8	3.0	MEDIUM	`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	3.9	1.4	[email protected]
7.5	2.0	HIGH	`AV:N/AC:L/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	10.0	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.8

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.9

[email protected]

5.8

3.0

MEDIUM

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

3.9

1.4

[email protected]

7.5

2.0

HIGH

AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

10.0

6.4

[email protected]

Affected software / configurations for CVE-2019-0002

Vendor	Product	Version	Raw CPE
juniper	junos	15.1x53	cpe:2.3:o:juniper:junos:15.1x53:d50::::::
juniper	junos	15.1x53	cpe:2.3:o:juniper:junos:15.1x53:d51::::::
juniper	junos	15.1x53	cpe:2.3:o:juniper:junos:15.1x53:d52::::::
juniper	junos	15.1x53	cpe:2.3:o:juniper:junos:15.1x53:d55::::::
juniper	junos	15.1x53	cpe:2.3:o:juniper:junos:15.1x53:d57::::::
juniper	junos	15.1x53	cpe:2.3:o:juniper:junos:15.1x53:d58::::::
juniper	junos	15.1x53	cpe:2.3:o:juniper:junos:15.1x53:d59::::::
juniper	junos	18.1	cpe:2.3:o:juniper:junos:18.1:-::::::
juniper	junos	18.1	cpe:2.3:o:juniper:junos:18.1:r1::::::
juniper	junos	18.1	cpe:2.3:o:juniper:junos:18.1:r2::::::
juniper	junos	18.1	cpe:2.3:o:juniper:junos:18.1:r2-s1::::::
juniper	junos	18.1	cpe:2.3:o:juniper:junos:18.1:r2-s2::::::
juniper	junos	18.1	cpe:2.3:o:juniper:junos:18.1:r2-s4::::::
juniper	junos	18.2	cpe:2.3:o:juniper:junos:18.2:-::::::
juniper	junos	18.2	cpe:2.3:o:juniper:junos:18.2:r1::::::
juniper	junos	18.2	cpe:2.3:o:juniper:junos:18.2:r1-s3::::::
juniper	junos	18.2	cpe:2.3:o:juniper:junos:18.2:r1-s4::::::
juniper	junos	18.2	cpe:2.3:o:juniper:junos:18.2:r1-s5::::::

References for CVE-2019-0002

URL	Tags
http://www.securityfocus.com/bid/106669	Third Party Advisory VDB Entry
https://kb.juniper.net/JSA10901	Vendor Advisory
https://www.juniper.net/documentation/en_US/junos/topics/reference/command-summary/show-pfe-filter.html	Vendor Advisory

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2019-0002

Common vulnerability scoring system (CVSS) metrics for CVE-2019-0002

Weakness enumeration for CVE-2019-0002

Affected software / configurations for CVE-2019-0002

References for CVE-2019-0002