dbcve.org
JunosOperating system · Juniper

CVE-2019-0006

CRITICAL · 9.8 CVSS v3.1 Published 2019-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A certain crafted HTTP packet can trigger an uninitialized function pointer deference vulnerability in the Packet Forwarding Engine manager (fxpc) on all EX, QFX and MX Series devices in a Virtual Chassis configuration. This issue can result in a crash of the fxpc daemon or may potentially lead to remote code execution. This issue only occurs when the crafted packet it destined to the device. Affected releases are Juniper Networks Junos OS: 14.1X53 versions prior to 14.1X53-D47 on EX and QFX Virtual Chassis Platforms; 15.1 versions prior to 15.1R7-S3 all Virtual Chassis Platforms 15.1X53 versions prior to 15.1X53-D50 on EX and QFX Virtual Chassis Platforms.

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 confidence

An uninitialized function pointer dereference vulnerability in the Packet Forwarding Engine manager (fxpc) daemon on Juniper EX, QFX, and MX Series devices in Virtual Chassis configurations can be triggered by a specially crafted HTTP packet destined to the device, potentially causing daemon crash or remote code execution.

MitigationUpgrade Junos OS to patched versions (14.1X53-D47+, 15.1R7-S3+, or 15.1X53-D50+ depending on platform) for affected Virtual Chassis deployments. If patching is not immediately feasible, restrict access to management interfaces and block external HTTP traffic to device IPs.

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
JunosOperating system
Affected:= 14.1x53= 15.1= 15.1x53

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Junos OS version
    Run 'show version' or 'show version detail' on the device CLI to retrieve the exact Junos version
    Affected if Version matches 14.1x53, 15.1, or 15.1x53 (any variant within these branches)
  2. Verify Virtual Chassis configuration
    Run 'show virtual-chassis' and 'show virtual-chassis configuration' to confirm the device is part of a Virtual Chassis deployment
    Affected if Device is configured as a Virtual Chassis member (vc-mode is enabled)
  3. Confirm HTTP service exposure
    Run 'show configuration system services' to review enabled management services, and check if HTTP (port 80) is listening on external interfaces
    Affected if HTTP service is enabled and reachable from untrusted networks
  4. Check fxpc daemon status
    Run 'show system processes' or 'request system process' commands to verify the fxpc daemon is running
    Affected if fxpc daemon is active on the device

Device is vulnerable if it runs an affected Junos version (14.1x53, 15.1, or 15.1x53), is configured in a Virtual Chassis, and has HTTP service exposed to network attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to patched versions (14.1X53-D47+, 15.1R7-S3+, or 15.1X53-D50+ depending on platform) for affected Virtual Chassis deployments. If patching is not immediately feasible, restrict access to management interfaces and block external HTTP traffic to device IPs.

Recommended fix High confidence

Upgrade to 14.1X53-D47+/15.1R7-S3+/15.1X53-D50+ depending on the base version (14.1X53/15.1/15.1X53)

  1. 1. Identify the current Junos OS version on the affected device using 'show version'
  2. 2. Determine the Virtual Chassis configuration type (EX, QFX, or MX Series)
  3. 3. For 14.1X53 releases: Plan upgrade to 14.1X53-D47 or later
  4. 4. For 15.1 releases: Plan upgrade to 15.1R7-S3 or later
  5. 5. For 15.1X53 releases: Plan upgrade to 15.1X53-D50 or later
  6. 6. Schedule a maintenance window for the upgrade procedure
  7. 7. Back up the current configuration using 'request system snapshot'
  8. 8. Download the appropriate Junos software upgrade package from the Juniper Networks support portal
Caveat Review Juniper release notes for any compatibility or configuration changes between current and target versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0006 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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