# CVE-2020-27339: Memory corruption in n/a

> Attackers can corrupt firmware or OS memory via improper validation in InsydeH2O SMM drivers, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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 Jun 2021
- **Updated:** 11 Aug 2026
- **Also known as:** CVE-2021-41610, GHSA-67f6-6h83-3w53

## What is CVE-2020-27339?

CVE-2020-27339 is a medium-severity memory corruption vulnerability in Insyde Insydeh2o, published on 16 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the kernel in Insyde InsydeH2O 5.x, certain SMM drivers did not correctly validate the CommBuffer and CommBufferSize parameters, allowing callers to corrupt either the firmware or the OS memory. The fixed versions for this issue in the AhciBusDxe, IdeBusDxe, NvmExpressDxe, SdHostDriverDxe, and SdMmcDeviceDxe drivers are 05.16.25, 05.26.25, 05.35.25, 05.43.25, and 05.51.25 (for Kernel 5.1 through 5.5).

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2020-27339?

It affects 17 products.


Products: Insyde Insydeh2o, Siemens Ruggedcom Apr1808 Firmware, Siemens Simatic Field Pg M5 Firmware, Siemens Simatic Field Pg M6 Firmware, Siemens Simatic Ipc127e Firmware, Siemens Simatic Ipc227g Firmware, Siemens Simatic Ipc277g Firmware, Siemens Simatic Ipc327g Firmware, Siemens Simatic Ipc377g Firmware, Siemens Simatic Ipc427e Firmware, Siemens Simatic Ipc477e Firmware, Siemens Simatic Ipc477e Pro Firmware, Siemens Simatic Ipc627e Firmware, Siemens Simatic Ipc647e Firmware, Siemens Simatic Ipc677e Firmware, Siemens Simatic Ipc847e Firmware, Siemens Simatic Itp1000 Firmware.

## How do I fix CVE-2020-27339?

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

## Is CVE-2020-27339 being exploited?

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

## Other vulnerabilities in Insyde Insydeh2o

- [CVE-2021-41842](https://insights.sbomify.com/CVE-2021-41842/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-22612](https://insights.sbomify.com/CVE-2023-22612/): Memory corruption in n/a (high 8.8)
- [CVE-2023-22613](https://insights.sbomify.com/CVE-2023-22613/): Memory corruption in n/a (high 8.8)
- [CVE-2023-22614](https://insights.sbomify.com/CVE-2023-22614/): Memory corruption in n/a (high 8.8)
- [CVE-2023-22615](https://insights.sbomify.com/CVE-2023-22615/): Memory corruption in n/a (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-27339 and fix it if it is affected.

What it is: CVE-2020-27339 is a medium-severity memory corruption vulnerability in Insyde Insydeh2o, published on 16 Jun 2021. 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-2020-27339 in the wild and no public exploit code.

Affected product: Insyde Insydeh2o. 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-2020-27339/ (Markdown: https://insights.sbomify.com/CVE-2020-27339/index.md)
```

## Sources

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

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