# CVE-2021-28213: Hardcoded credentials in EDK II

> Hardcoded encrypted private keys in EDK II IpSecDxe.efi allow attackers to bypass IPsec security controls and potentially access protected data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-28213, GHSA-p38x-2cfm-g52f, UBUNTU-CVE-2021-28213

## What is CVE-2021-28213?

CVE-2021-28213 is a high-severity vulnerability in TianoCore EDK II, published on 11 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Example EDK2 encrypted private key in the IpSecDxe.efi present potential security risks.

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

It affects 1 product.


Products: Tianocore Edk2.

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

Apply the vendor's patch.

## Is CVE-2021-28213 being exploited?

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

## Other vulnerabilities in TianoCore EDK II

- [CVE-2023-45230](https://insights.sbomify.com/CVE-2023-45230/): Buffer Overflow in EDK II Network Package (high 8.3)
- [CVE-2023-45234](https://insights.sbomify.com/CVE-2023-45234/): Buffer Overflow in EDK II Network Package (high 8.3)
- [CVE-2023-45235](https://insights.sbomify.com/CVE-2023-45235/): Buffer Overflow in EDK II Network Package (high 8.3)
- [CVE-2021-28210](https://insights.sbomify.com/CVE-2021-28210/): Denial of service in EDK II (high 7.8)
- [CVE-2019-14584](https://insights.sbomify.com/CVE-2019-14584/): Null dereference in Tianocore EDK2 (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-28213 is a high-severity vulnerability in TianoCore EDK II, published on 11 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-28213 in the wild and no public exploit code.

Affected product: TianoCore EDK II. 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-28213/ (Markdown: https://insights.sbomify.com/CVE-2021-28213/index.md)
```

## Sources

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

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