dbcve.org
EnvoyApplication · Enphase

CVE-2019-7678

CRITICAL · 9.8 CVSS v3.0 Published 2019-02-09
Fix available
A fix is available. Upgrade to after 3.9.0 or later.
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 directory traversal vulnerability was discovered in Enphase Envoy R3.*.* via images/, include/, include/js, or include/css on TCP port 8888.

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

A directory traversal vulnerability in Enphase Envoy R3 devices allows remote attackers to access arbitrary files on the system by using path traversal sequences (e.g., ../) in requests to the images/, include/, include/js, or include/css directories on TCP port 8888. This enables unauthorized file system access with high severity due to the critical CVSS score.

MitigationApply the vendor-supplied firmware update to the Enphase Envoy R3 to patch the directory traversal vulnerability; if immediate patching is not feasible, implement network segmentation and firewall rules to restrict untrusted access to TCP port 8888.

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
EnvoyApplication
Affected:>= 3.0.0, <= 3.9.0

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.0/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. Identify Enphase Envoy R3 devices on the network
    Locate devices by accessing the web interface or checking network inventory for Enphase Envoy model R3. The device typically presents a web UI on ports 80/443 or 8888.
    Affected if The device is an Enphase Envoy R3 model
  2. Check the installed firmware version
    Access the Envoy web interface and navigate to the firmware information page, or query the device API endpoint /api/v1/production.json to retrieve version details. Compare the firmware version against the affected range 3.0.0 to 3.9.0.
    Affected if The firmware version falls within >= 3.0.0 and <= 3.9.0
  3. Verify TCP port 8888 accessibility
    Scan the device using nmap or netcat to confirm port 8888 is open and reachable. Example: nmap -p 8888 <device_ip> or nc -zv <device_ip> 8888.
    Affected if TCP port 8888 is exposed and accessible from the network segment being assessed
  4. Inspect for directory traversal exposure
    Send an HTTP GET request to the vulnerable paths using path traversal sequences, for example: GET http://<device_ip>:8888/include/../../../etc/passwd HTTP/1.1. Check if the response contains file contents from outside the web root directory.
    Affected if The device returns file contents from outside the intended directories, indicating successful path traversal

A user is affected if they have an Enphase Envoy R3 device running firmware version 3.0.0 to 3.9.0 with TCP port 8888 accessible and the directory traversal vulnerability confirmed.

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
Upgrade available Upgrade to a release after 3.9.0
Interim mitigation

Apply the vendor-supplied firmware update to the Enphase Envoy R3 to patch the directory traversal vulnerability; if immediate patching is not feasible, implement network segmentation and firewall rules to restrict untrusted access to TCP port 8888.

Recommended fix Moderate confidence

Enphase Envoy R3 firmware version > 3.9.0 (e.g., latest stable 3.x release or 4.x if available)

  1. Identify the current Envoy R3 firmware version through the web interface or administrative console
  2. Access the Enphase Enlighten cloud portal or local administration panel
  3. Check for available firmware updates - look for versions beyond 3.9.0
  4. Download and apply the latest stable Envoy firmware from Enphase's official firmware distribution
  5. After upgrade, verify the fix by attempting to access paths like ../ or ../../ through the affected endpoints on port 8888
  6. Confirm the web server returns access denied or proper error rather than directory contents
Caveat IoT firmware upgrades may reset device configuration; re-register device with Enphase Enlighten after upgrade if needed

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

Fix this in Envoy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7678 — 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-7678 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