dbcve.org
Iq Gateway FirmwareOperating system · Enphase

CVE-2024-21879

HIGH · 8.8 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 8.2.4225 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Neutralization of Special Elements used in a Command ('Command Injection') vulnerability through an url parameter of an authenticated enpoint in Enphase IQ Gateway (formerly known as Envoy) allows OS Command Injection.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

Command injection vulnerability in Enphase IQ Gateway (Envoy) firmware allows authenticated users to execute arbitrary OS commands through unsanitized url parameters in a specific endpoint. Affected versions range from 4.x to 8.x, with the vulnerability patched in version 8.2.4225 and later.

MitigationUpdate Enphase IQ Gateway firmware to version 8.2.4225 or later. Until patched, restrict administrative access to trusted networks only to limit exposure to authenticated attackers.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Enphase IQ Gateway firmware version
    Access the Envoy web interface and navigate to the About or System Information page, or use the enphasegateway.local API endpoint to retrieve firmware version information
    Affected if The displayed firmware version is 4.0 or higher but lower than 8.2.4225
  2. Verify firmware version via CLI or API
    Query the local API at http://<gateway-ip>/api/v1/production.json or check /etc/version file via SSH if available
    Affected if Version returned is in the range 4.0 to 8.2.4224 (inclusive)
  3. Confirm web interface authentication status
    Check if the Envoy administrative interface requires login credentials by accessing the login page
    Affected if The web interface is accessible without authentication or uses default/weak credentials, allowing unauthenticated or low-privilege access
  4. Identify exposed management interfaces
    Scan network for open ports on the gateway device (typically ports 80, 443, 8080, 8443) and check if the Envoy API is reachable from untrusted networks
    Affected if The administrative interface is exposed to networks beyond trusted local networks

You are affected if your Enphase IQ Gateway firmware version is 4.0 or higher but lower than 8.2.4225 AND the web management interface is accessible to untrusted users, allowing authenticated command injection via URL parameters.

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

Update Enphase IQ Gateway firmware to version 8.2.4225 or later. Until patched, restrict administrative access to trusted networks only to limit exposure to authenticated attackers.

Recommended fix High confidence

8.2.4225 or later

  1. 1. Download the latest Enphase IQ Gateway firmware version 8.2.4225 or later from the official Enphase support site
  2. 2. Ensure you have a backup of the current configuration
  3. 3. Access the IQ Gateway administrative interface
  4. 4. Navigate to the firmware update section
  5. 5. Upload and apply the firmware version 8.2.4225 or later
  6. 6. Verify the firmware version after update completes
  7. 7. Test that the previously vulnerable endpoint is no longer exploitable
Caveat Review Enphase release notes for any configuration changes required between your current version and the target 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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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