CVE-2021-22766
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 · uneditedA CWE-20: Improper Input Validation vulnerability exists in PowerLogic EGX100 (Versions 3.0.0 and newer) and PowerLogic EGX300 (All Versions) that could cause denial of service via a specially crafted HTTP packet
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 confidenceImproper input validation in the web interface of PowerLogic EGX100 (v3.0.0+) and EGX300 allows remote attackers to cause denial of service by sending specially crafted HTTP packets that trigger the device to become unresponsive or crash.
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>= 3.0.0all versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device modelAccess the device web interface or check network inventory to confirm whether the device is a PowerLogic EGX100 or EGX300. The model information is typically displayed on the device login page or in the device status/diagnostics page.Affected if The device is confirmed to be a Schneider Electric PowerLogic EGX100 or EGX300.
-
Determine the firmware version on EGX100Log into the EGX100 web interface and navigate to the 'About' or 'Device Information' page to view the installed firmware version. Compare the version number against the affected range (>= 3.0.0).Affected if The EGX100 firmware version is 3.0.0 or higher.
-
Confirm EGX300 is affectedFor EGX300 devices, verify the device model and note that all firmware versions are affected according to the CVE advisory. Check the firmware version via the web interface for documentation purposes.Affected if The device is an EGX300 regardless of firmware version.
-
Verify the web interface is enabledAttempt to access the device via HTTP (port 80) or HTTPS (port 443) using a web browser. Confirm the login page or device status page loads successfully, indicating the web interface is active.Affected if The web interface is accessible and responds to HTTP requests.
-
Check network exposure of HTTP serviceUse a network scanner or check firewall rules to determine if the device HTTP port (80/443) is exposed to untrusted networks or the public internet. Verify whether access is restricted to authorized management networks only.Affected if The device HTTP web interface is accessible from untrusted networks or the internet.
The environment is affected if the device is a PowerLogic EGX100 (firmware >= 3.0.0) or EGX300 (any version) with the web interface enabled and accessible, particularly if exposed to untrusted networks.
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 available firmware updates from Schneider Electric; if no patch exists, isolate devices behind a firewall or VPN, and restrict HTTP access to authorized management networks only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22766 — 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-2021-22766 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