CVE-2021-27430
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 bootloader binary Version 7.00, 7.01 and 7.02 included unused hardcoded credentials. Additionally, a user with physical access to the UR IED can interrupt the boot sequence by rebooting the UR.
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 confidenceThe GE UR (Universal Relay) IED bootloader versions 7.00, 7.01, and 7.02 contain unused hardcoded credentials embedded in the binary, which could allow unauthorized access if exploited. Additionally, an attacker with physical access can interrupt the boot sequence by rebooting the device during startup.
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= 7.00= 7.01= 7.02CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 device modelLocate the physical device or system documentation to confirm it is a GE UR (Universal Relay) IED (Intelligent Electronic Device). Check the device nameplate, asset inventory, or management interface for the model identifier.Affected if The device is not a GE UR series relay, then this CVE does not apply.
-
Determine the bootloader versionAccess the device firmware/bootloader information through the device console, management interface, or firmware file metadata. On the GE UR, this is typically shown during boot-up or available via the device configuration software.Affected if The bootloader version cannot be determined, assume it may be affected and treat as vulnerable.
-
Compare against affected versionsCompare the identified bootloader version to the affected range: exactly 7.00, 7.01, or 7.02. Note that only these three specific versions are vulnerable.Affected if The bootloader version is 7.00, 7.01, or 7.02, then the device contains the unused hardcoded credentials vulnerability.
-
Assess physical access controlsEvaluate whether the device is deployed in a physically secure location with controlled access. Determine if an unauthorized person could physically access the device to reboot it during the boot sequence.Affected if Physical access controls are absent or insufficient, the boot sequence interruption vulnerability is present regardless of version.
A user is affected if the GE UR bootloader version is exactly 7.00, 7.01, or 7.02, or if the device has insufficient physical access controls regardless of version.
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-provided firmware updates to replace the vulnerable bootloader and implement physical access controls to prevent unauthorized physical interaction with the device.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.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,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27430 — 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-27430 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