CVE-2019-0008
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 · uneditedA certain sequence of valid BGP or IPv6 BFD packets may trigger a stack based buffer overflow in the Junos OS Packet Forwarding Engine manager (FXPC) process on QFX5000 series, EX4300, EX4600 devices. This issue can result in a crash of the fxpc daemon or may potentially lead to remote code execution. Affected releases are Juniper Networks Junos OS on QFX 5000 series, EX4300, EX4600 are: 14.1X53; 15.1X53 versions prior to 15.1X53-D235; 17.1 versions prior to 17.1R3; 17.2 versions prior to 17.2R3; 17.3 versions prior to 17.3R3-S2, 17.3R4; 17.4 versions prior to 17.4R2-S1, 17.4R3; 18.1 versions prior to 18.1R3-S1, 18.1R4; 18.2 versions prior to 18.2R2; 18.2X75 versions prior to 18.2X75-D30; 18.3 versions prior to 18.3R2.
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 confidenceStack-based buffer overflow in the Packet Forwarding Engine manager (FXPC) process on QFX5000 series, EX4300, and EX4600 switches. Triggered by a specific sequence of valid BGP or IPv6 BFD packets, this vulnerability can cause the fxpc daemon to crash or potentially allow remote code execution with critical severity (CVSS 9.8).
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, < 15.1x53-d235>= 17.1, < 17.1r3>= 17.2, < 17.2r3>= 17.3, < 17.3r3-s2>= 17.4, < 17.4r2-s1>= 18.1, < 18.1r3-s1>= 18.2, < 18.2r2>= 18.2x75, < 18.2x75-d30>= 18.3, < 18.3r2= 14.1x53= 17.3= 17.4CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify the switch modelRun 'show chassis hardware' or 'show version' to confirm the device is a QFX5000 series, EX4300, or EX4600 switchAffected if The device model is one of QFX5000, EX4300, or EX4600 series
-
Check the installed Junos versionRun 'show version' and locate the Junos OS version string (for example, 15.1X53-D45, 17.2R1.9, 18.2R1)Affected if The installed version falls within any of these ranges: 15.1X53 to 15.1X53-D234, 17.1 to 17.1R2, 17.2 to 17.2R2, 17.3 to 17.3R3-S1, 17.4 to 17.4R2, 18.1 to 18.1R3, 18.2 to 18.2R1, 18.2X75 to 18.2X75-D29, 18.3 to 18.3R1, or equals exactly 14.1X53-D, 17.3, or 17.4
-
Verify BGP is configuredRun 'show configuration protocols bgp' and check for active BGP groups or neighborsAffected if BGP is configured and active with established peers
-
Verify IPv6 BFD is configuredRun 'show configuration protocols bfd' and look for IPv6 BFD sessions (bfd-liveness-detection under family inet6)Affected if IPv6 BFD sessions are configured under the inet6 family
-
Confirm fxpc daemon is runningRun 'show system processes' or 'request system process' to verify the fxpc process is activeAffected if The fxpc daemon is running on the device
The environment is affected if the device is a QFX5000, EX4300, or EX4600 switch running a Junos version within the affected ranges AND has BGP or IPv6 BFD configured with the fxpc daemon active.
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.
dbcve · scoped15.1x53-d23517.1r317.2r3
Apply the vendor-supplied Junos OS updates for affected versions (15.1X53-D235, 17.1R3, 17.2R3, 17.3R3-S2/17.3R4, 17.4R2-S1/17.4R3, 18.1R3-S1/18.1R4, 18.2R2, 18.2X75-D30, 18.3R2 or later). Prior to patching, implement network-level access controls to limit BGP and BFD traffic to trusted peers only.
15.1X53-D235 (or later 15.1X53), 17.1R3 (or later 17.1), 17.2R3 (or later 17.2), 17.3R3-S2/17.3R4 (or later 17.3) - select the appropriate fixed version based on your current branch
- 1. Identify the current Junos OS version on the affected device by running: show version
- 2. Determine which version branch you are currently running (e.g., 15.1X53, 17.1, 17.2, 17.3)
- 3. Download the appropriate fixed Junos software release from Juniper Networks support portal: 15.1X53-D235 or later for 15.1X53 branch; 17.1R3 or later for 17.1 branch; 17.2R3 or later for 17.2 branch; 17.3R3-S2, 17.3R4, or later for 17.3 branch
- 4. Transfer the software package to the device using FTP/SCP or USB
- 5. Install the software upgrade using: request system software add <package-name> reboot
- 6. After the device reboots, verify the new version is installed: show version
- 7. Verify the fxpc process is running normally: show system processes | match fxpc
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0008 — 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-0008 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