CVE-2019-0009
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOn EX2300 and EX3400 series switches, high disk I/O operations can disrupt communication between the routing engine (RE) and packet forwarding engine (PFE). In virtual chassis deployments, this issue disrupts inter-member communication, effectively causing a denial of service. The vulnerability is fixed in Junos OS versions 15.1X53-D590 and later, 18.1R2-S2/18.1R3 and later, and 18.2R2 and later.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 15.1x53= 18.1= 18.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm EX2300 or EX3400 hardware modelRun 'show chassis hardware' and locate the model number in the outputAffected if Model is not EX2300 or EX3400 (different models are not affected by this CVE)
-
Identify installed Junos OS versionRun 'show version' and note the Junos OS release number (for example, 15.1X53-D30, 18.1R1, 18.2R1)Affected if Version is 15.1X53 before D590, or 18.1 before R2-S2/R3, or 18.2 before R2 (unpatched versions in the affected ranges)
-
Check for virtual chassis configurationRun 'show virtual-chassis' to determine if the switch is part of a virtual chassis deploymentAffected if Virtual chassis is configured (the DoS impact specifically affects inter-member communication in virtual chassis setups)
-
Look for PFE communication symptomsRun 'show pfem stats' and 'show virtual-chassis member-status' to check for errors or member communication failuresAffected if PFE errors or member communication failures are present, indicating the disk I/O issue may be disrupting RE-to-PFE or inter-member communication
If the device is an EX2300 or EX3400 running an unpatched Junos version (15.1X53 before D590, 18.1 before R2-S2/R3, or 18.2 before R2) and configured as virtual chassis with observable communication failures, the environment is affected by CVE-2019-0009.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Junos OS on affected EX2300 and EX3400 switches to the fixed releases (15.1X53-D590, 18.1R2-S2, 18.1R3, or 18.2R2 and later). In virtual chassis deployments, ensure all members are upgraded to maintain consistent communication.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0009 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-0009 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data