dbcve.org
Iq Gateway FirmwareOperating system · Enphase

CVE-2024-21876

CRITICAL · 9.1 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 8.2.4225 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability via a URL parameter in Enphase IQ Gateway (formerly known as Envoy) allows an unautheticated attacker to access or create arbitratry files.This issue affects Envoy: from 4.x to 8.x and < 8.2.4225.

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

Path traversal vulnerability in Enphase IQ Gateway firmware allows unauthenticated remote attackers to access or create arbitrary files on the system by manipulating URL parameters. This critical flaw affects Envoy versions 4.x through 8.x and versions prior to 8.2.4225.

MitigationApply vendor firmware update to version 8.2.4225 or later; if immediate patching is not feasible, implement network segmentation and restrict external access to the IQ Gateway management interface.

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
Iq Gateway FirmwareOperating system
Affected:>= 4.0, < 8.2.4225

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 the device as an Enphase IQ Gateway
    Access the web management interface of the device or check network documentation to confirm the device model is Enphase IQ Gateway (Envoy). Look for Enphase branding or check the device's HTTP server banner.
    Affected if The device is an Enphase IQ Gateway (Envoy) unit.
  2. Check the firmware version
    Log into the IQ Gateway web interface and navigate to the firmware or system information page. Alternatively, check the response headers or the HTML title/page content for version information.
    Affected if The installed firmware version is 4.0 or higher but lower than 8.2.4225.
  3. Verify the web management interface is accessible
    Attempt to access the IQ Gateway HTTP/HTTPS management interface from the network segment where the device is deployed. Confirm the login page or status page loads.
    Affected if The web management interface is reachable on the network (required for the path traversal to be exploitable).

The environment is affected if an Enphase IQ Gateway is running firmware version 4.0 or higher but below 8.2.4225, and its web management interface is network-accessible.

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 8.2.4225 or later
Fixed in 8.2.4225
Interim mitigation

Apply vendor firmware update to version 8.2.4225 or later; if immediate patching is not feasible, implement network segmentation and restrict external access to the IQ Gateway management interface.

Recommended fix High confidence

Enphase IQ Gateway firmware version 8.2.4225 or later

  1. Check current firmware version through the IQ Gateway admin interface or API
  2. Download the firmware update (version 8.2.4225 or later) from the official Enphase vendor portal
  3. Back up current device configuration if possible
  4. Upload and apply the firmware update through the IQ Gateway admin interface or using the vendor-provided upgrade mechanism
  5. Verify the device reboots successfully and runs the patched firmware version
  6. Confirm the vulnerability is resolved by checking the firmware version displays 8.2.4225 or higher
Caveat Review Enphase release notes for any configuration or compatibility changes between your current version and 8.2.4225+ before upgrading

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

Fix this in Iq Gateway Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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