# CVE-2022-34413: Memory corruption in PowerEdge Platform

> A local attacker with high privileges can exploit improper SMM buffer verification in Dell BIOS to execute arbitrary code or cause denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2023
- **Updated:** 26 Feb 2025
- **Also known as:** GHSA-95hj-53q6-wvxf

## What is CVE-2022-34413?

CVE-2022-34413 is a high-severity memory corruption vulnerability in Dell PowerEdge Platform, published on 16 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dell PowerEdge BIOS and Dell Precision BIOS contain an Improper SMM communication buffer verification vulnerability. A local malicious user with high Privileges may potentially exploit this vulnerability to perform arbitrary code execution or cause denial of service.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2022-34413?

It affects 80 products.


Products: Dell C4130 Firmware, Dell C4140 Firmware, Dell C6320 Firmware, Dell C6420 Firmware, Dell C6520 Firmware, Dell C6525 Firmware, Dell Dss8440 Firmware, Dell Fc430 Firmware, Dell Fc630 Firmware, Dell Fc640 Firmware, Dell Fc830 Firmware, Dell M630 Firmware, Dell M630p Firmware, Dell M640 Firmware, Dell M640p Firmware, Dell M830 Firmware, Dell M830p Firmware, Dell Mx740c Firmware, Dell Mx750c Firmware, Dell Mx840c Firmware and 60 more.

## How do I fix CVE-2022-34413?

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

## Is CVE-2022-34413 being exploited?

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

## Other vulnerabilities in Dell PowerEdge Platform

- [CVE-2022-34406](https://insights.sbomify.com/CVE-2022-34406/): Memory corruption in PowerEdge Platform (high 7.5)
- [CVE-2022-34407](https://insights.sbomify.com/CVE-2022-34407/): Memory corruption in PowerEdge Platform (high 7.5)
- [CVE-2022-34408](https://insights.sbomify.com/CVE-2022-34408/): Memory corruption in PowerEdge Platform (high 7.5)
- [CVE-2022-34409](https://insights.sbomify.com/CVE-2022-34409/): Memory corruption in PowerEdge Platform (high 7.5)
- [CVE-2022-34410](https://insights.sbomify.com/CVE-2022-34410/): Memory corruption in PowerEdge Platform (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34413 and fix it if it is affected.

What it is: CVE-2022-34413 is a high-severity memory corruption vulnerability in Dell PowerEdge Platform, published on 16 Mar 2023. 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-2022-34413 in the wild and no public exploit code.

Affected product: Dell PowerEdge Platform. 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-2022-34413/ (Markdown: https://insights.sbomify.com/CVE-2022-34413/index.md)
```

## Sources

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

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