CVE-2024-21880
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 · uneditedImproper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability via the url parameter of an authenticated enpoint in Enphase IQ Gateway (formerly known as Enphase) allows OS Command Injection.This issue affects Envoy: 4.x <= 7.x
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 · moderate confidenceAuthenticated OS command injection vulnerability in Enphase IQ Gateway (Envoy 4.x-7.x) allows attackers to execute arbitrary commands via the url parameter of an authenticated endpoint due to improper neutralization of special elements used in system commands.
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>= 4.0, <= 7.3.120CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Enphase IQ Gateway firmware versionAccess the device's admin web interface or use the enphase utility command (e.g., 'enphase -v' or check /etc/version on the device) to retrieve the installed firmware versionAffected if The firmware version is >= 4.0 and <= 7.3.120
-
Confirm the device model is EnvoyCheck the device label or web interface to confirm the model is an Enphase Envoy (IQ Gateway) productAffected if The device is an Envoy IQ Gateway model
-
Determine if the authenticated management interface is network-accessibleReview firewall rules, router port forwards, or VPN configurations to check whether the Envoy admin web interface (typically ports 80/443 or 8080/8443) is exposed to untrusted networksAffected if The authenticated admin interface is accessible from untrusted networks
-
Check for suspicious entries in device logs or http access logsReview the Envoy's web server access logs and system logs for unusual requests to endpoints that accept a 'url' parameter, especially containing shell metacharacters like ; | ` $ ( )Affected if Logs show requests to authenticated endpoints with url parameters containing shell command syntax
The environment is affected if the Enphase IQ Gateway firmware is version 4.0 through 7.3.120 and the authenticated management interface is network-accessible to attackers.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor patch when available; if no patch, restrict network access to authenticated management interfaces and implement strict input validation/allow-listing on all parameters.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21880 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21880 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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