Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2019-0009

Junos OS: EX2300 and EX3400: High disk I/O operations may disrupt the communication between RE and PFE

Medium5.5EPSS 0.35%
Published
Updated
Reserved
Assigned by
juniper

Description

On EX2300 and EX3400 series, high disk I/O operations may disrupt the communication between the routing engine (RE) and the packet forwarding engine (PFE). In a virtual chassis (VC) deployment, this issue disrupts communication between the VC members. This issue does not affect other Junos platforms. Affected releases are Junos OS on EX2300 and EX3400 series: 15.1X53 versions prior to 15.1X53-D590; 18.1 versions prior to 18.1R2-S2, 18.1R3; 18.2 versions prior to 18.2R2.

Timeline

  1. ID reserved

    By juniper

  2. · 3 months later

    Published

  3. · 6 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2019-0009, by who scored it
Scored byCVSSScoreVector
juniperCNA (assigner)3.0Medium5.5CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.35% · top 71% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

  • DoS

Affected products

  • Juniper Networks · Junos OS

    • affected 15.1X53 – < 15.1X53-D113, 15.1X53-D590
    • affected 18.1 – < 18.1R2-S2, 18.1R3
    • affected 18.2 – < 18.2R2

What to do

Solution: The following software releases have been updated to resolve this specific issue: Junos OS 15.1X53-D113, 15.1X53-D590, 18.1R2-S2, 18.1R3, 18.2R2, 18.3R1, and all subsequent releases.

Workaround: Avoid performing operation that may generate high disk I/O. Limiting the access to the device to only trusted administrators from trusted administrative networks or hosts would minimize the risk.

References (2)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2019-0009 badge
[![CVE-2019-0009](https://trackcve.app/badge/CVE-2019-0009.svg)](https://trackcve.app/cve/CVE-2019-0009)

Record last updated .