CVE-2019-0008: QFX5000 Series, EX4300, EX4600: A stack buffer overflow vulnerability in Packet Forwarding Engine manager (FXPC) process
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.5% (FIRST EPSS); higher than 91.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A 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.
- Published
- Apr 10, 2019
- Updated
- Jun 16, 2026
- EPSS
- 4.5% · 91th percentile
- CWE
- CWE-121
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.5%
CNA vs NVD score
- NVD
- 9.8
- CNA · juniper
- 9.8
- agree
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| juniper | junos | cpe:2.3:o:juniper:junos |
| juniper | ex4300 | cpe:2.3:h:juniper:ex4300 |
| juniper | ex4300m | cpe:2.3:h:juniper:ex4300m |
| juniper | ex4600 | cpe:2.3:h:juniper:ex4600 |
| juniper | ex4650 | cpe:2.3:h:juniper:ex4650 |
| juniper | qfx5100 | cpe:2.3:h:juniper:qfx5100 |
| juniper | qfx5110 | cpe:2.3:h:juniper:qfx5110 |
| juniper | qfx5120 | cpe:2.3:h:juniper:qfx5120 |
| juniper | qfx5200-32c | cpe:2.3:h:juniper:qfx5200-32c |
| juniper | qfx5200-48y | cpe:2.3:h:juniper:qfx5200-48y |
| juniper | qfx5210-64c | cpe:2.3:h:juniper:qfx5210-64c |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junos15.1x53 and later · before 15.1x53-d235
- juniper junos17.1 and later · before 17.1r3
- juniper junos17.2 and later · before 17.2r3
- juniper junos17.3 and later · before 17.3r3-s2
- juniper junos17.4 and later · before 17.4r2-s1
- juniper junos18.1 and later · before 18.1r3-s1
- juniper junos18.2 and later · before 18.2r2
- juniper junos18.2x75 and later · before 18.2x75-d30
- juniper junos18.3 and later · before 18.3r2
- juniper junos14.1x53
- juniper junos17.3
- juniper junos17.4
- juniper junos18.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (juniper). Independent of NVD's CPE analysis and usually ahead of it.
Juniper Networks Junos OS
- 14.1X53affected
- 15.1X53 and later · before 15.1X53-D235affected
- 17.1 and later · before 17.1R3affected
- 18.1 and later · before 18.1R3-S1, 18.1R4affected
- 18.2 and later · before 18.2R2affected
- 18.3 and later · before 18.3R2affected
- 17.2 and later · before 17.2R3affected
- 17.3 and later · before 17.3R3-S2, 17.3R4affected
- 17.4 and later · before 17.4R2-S1, 17.4R3affected
- 18.2X75 and later · before 18.2X75-D30affected
Same product
juniper: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-36845Junos OS: EX and SRX Series: A PHP vulnerability in J-Web allows an unauthenticated to control an important environment variableKEV98Now
- CVE-2023-36846Junos OS: SRX Series: A vulnerability in J-Web allows an unauthenticated attacker to upload arbitrary filesKEV79This week
- CVE-2023-36844Junos OS: EX Series: A PHP vulnerability in J-Web allows an unauthenticated attacker to control important environment variablesKEV78This week
Published before and after this one in the same product
- ← EarlierCVE-2019-0014Jan 15, 2019 · Junos OS: QFX and PTX Series: FPC process crashes after J-Flow processes a malformed packet31Monitor
- ← EarlierCVE-2019-0015Jan 15, 2019 · Junos OS: SRX Series: Deleted dynamic VPN users are allowed to establish VPN connections until reboot21Monitor
- Later →CVE-2019-0019Apr 10, 2019 · BGP packets can trigger rpd crash when BGP tracing is enabled.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-121 · Stack-based Buffer OverflowCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.