CVE-2021-27428
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 · uneditedGE UR IED firmware versions prior to version 8.1x supports upgrading firmware using UR Setup configuration tool – Enervista UR Setup. This UR Setup tool validates the authenticity and integrity of firmware file before uploading the UR IED. An illegitimate user could upgrade firmware without appropriate privileges. The weakness is assessed, and mitigation is implemented in firmware Version 8.10.
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 confidenceGE UR IED (Intelligent Electronic Device) firmware versions prior to 8.1x contain an authentication bypass vulnerability in the Enervista UR Setup configuration tool. The tool, which should validate firmware authenticity and integrity before upload, fails to properly enforce authorization checks, allowing unauthorized users to upgrade firmware without appropriate privileges. This is a critical privilege escalation vulnerability with CVSS 9.8 that could allow attackers to modify device firmware on affected GE protection relays.
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< 8.10< 8.10< 8.10< 8.10< 8.10< 8.10< 8.10< 8.10CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 GE Multilin device modelLocate the device nameplate or check the device web interface or Enervista UR Setup software for the model identifier (B30, B90, C60, C70, C95, D30, D60, or F35)Affected if The device is one of the listed GE Multilin models (B30, B90, C60, C70, C95, D30, D60, or F35)
-
Determine the installed firmware versionAccess the device via Enervista UR Setup software and navigate to the Device Information or System Status section, or check the device web interface under the firmware or version information panelAffected if The displayed firmware version is below 8.10 (for example, 8.00, 7.x, or any version number less than 8.10)
-
Confirm the Enervista UR Setup tool is accessibleVerify that the Enervista UR Setup configuration tool is installed and network-accessible, typically on a workstation connected to the same network as the deviceAffected if The Enervista UR Setup tool is running and can communicate with the device
-
Check firmware version against the vulnerable thresholdCompare the installed firmware version number to the known affected range (all versions prior to 8.10)Affected if The firmware version is less than 8.10 (for example, 8.01, 8.02, 7.5, etc.)
A user is affected if they have a GE Multilin device (B30, B90, C60, C70, C95, D30, D60, or F35) running firmware version 8.x versions prior to 8.10, and the Enervista UR Setup tool is accessible.
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.
dbcve · scoped8.10
Upgrade GE UR IED firmware to version 8.10 or later as specified in the official mitigation. Prior to upgrade, conduct an impact assessment in a test environment to ensure compatibility with existing systems, and implement network segmentation controls to limit access to the UR Setup tool.
Firmware version 8.10 (or later 8.1x release)
- 1. Identify the exact Multilin model (B30, B90, C60, C70, C95, D30, D60, or F35) from the physical device or documentation
- 2. Access the device interface and record the current firmware version to confirm it is below 8.10
- 3. Download firmware version 8.10 or later from the official GE Grid Solutions portal (www.gegridsolutions.com) - ensure the firmware matches your specific model number
- 4. Launch Enervista UR Setup configuration tool and connect to the device following standard procedures
- 5. Use the firmware upgrade function in Enervista UR Setup to upload the 8.10+ firmware file to the device
- 6. Wait for the firmware upgrade process to complete - do not power off the device during this process
- 7. After reboot, verify the new firmware version is 8.10 or later via the device interface or Enervista UR Setup
- 8. Confirm the device is operating normally and all protection functions are functioning as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27428 — 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-27428 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