# CVE-2021-27430: GE UR family hardcoded credentials

> Hardcoded credentials in GE UR bootloader allow attackers with physical access to bypass security controls and escalate privileges.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-v3x3-gpvq-h27p

## What is CVE-2021-27430?

CVE-2021-27430 is a high-severity vulnerability in GE UR bootloader binary, published on 23 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GE 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2021-27430?

It affects 1 product.


Products: Ge Ur Bootloader Binary.

## How do I fix CVE-2021-27430?

No fix has been published for CVE-2021-27430 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-27430 being exploited?

There is no known exploitation of CVE-2021-27430 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-27430 and fix it if it is affected.

What it is: CVE-2021-27430 is a high-severity vulnerability in GE UR bootloader binary, published on 23 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-27430 in the wild and no public exploit code.

Affected product: GE UR bootloader binary. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-27430/ (Markdown: https://insights.sbomify.com/CVE-2021-27430/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-27430
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-27430
- OSV: https://osv.dev/vulnerability/CVE-2021-27430

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-27430/
Summaries are generated and may contain mistakes; the official description above is the record.