dbcve.org
Iq Gateway FirmwareOperating system · Enphase

CVE-2024-21877

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 8.2.4225 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 through a url parameter in Enphase IQ Gateway (formerly known as Envoy) allows File Manipulation. The endpoint requires authentication.This issue affects Envoy: from 4.x to 8.0 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 (Envoy) firmware allows authenticated users to manipulate files through a vulnerable URL parameter. The flaw exists in versions 4.x through 8.0 and versions prior to 8.2.4225, allowing improper limitation of pathname to restricted directories.

MitigationUpgrade IQ Gateway firmware to version 8.2.4225 or later. Until patched, restrict network access to the management interface and enforce strict authentication policies.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Determine IQ Gateway firmware version
    Access the Enphase installer or consumer portal, or log into the IQ Gateway local web interface and navigate to the firmware or system information page to retrieve the current firmware version number.
    Affected if The installed firmware version is 4.0 or higher but lower than 8.2.4225.
  2. Verify web management interface is accessible
    Confirm that the IQ Gateway web interface (typically on ports 80 or 443) is reachable from the network. Attempt to access the login page via HTTP/HTTPS.
    Affected if The web management interface is exposed and accessible on the network.
  3. Confirm authentication is required for the web interface
    Test whether the web interface enforces login by attempting to access protected endpoints or parameters without providing credentials.
    Affected if The interface allows unauthenticated access or uses default/weak credentials.
  4. Inspect web server access logs for path traversal patterns
    Review IQ Gateway logs (if accessible) for suspicious URL patterns containing sequences like ../, ..\, or absolute path references in query parameters.
    Affected if Log entries show path traversal attempts (e.g., /../../etc/passwd) targeting the affected URL parameter.
  5. Assess network exposure of management interface
    Determine if the IQ Gateway management interface is exposed to the public internet or untrusted networks by reviewing firewall rules, NAT configurations, or port scan results.
    Affected if The management interface is accessible from untrusted networks without VPN or IP restrictions.

You are affected if your IQ Gateway firmware version falls within 4.0 to 8.2.4224 (inclusive) and the web management interface is accessible, especially from untrusted networks.

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

Upgrade IQ Gateway firmware to version 8.2.4225 or later. Until patched, restrict network access to the management interface and enforce strict authentication policies.

Recommended fix Moderate confidence

Firmware version 8.2.4225 or later

  1. Access the Enphase IQ Gateway administrative interface
  2. Navigate to the firmware update section
  3. Check current firmware version to confirm it's affected (4.x to 8.0 or < 8.2.4225)
  4. Download firmware version 8.2.4225 or later from enphase.com support portal
  5. Initiate firmware upgrade process
  6. Allow upgrade to complete and verify new version

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

Fix this in Iq Gateway Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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