# CVE-2021-27480: Memory corruption in Delta Industrial Automation COMMGR

> A stack-based buffer overflow in Delta Industrial Automation COMMGR allows attackers to execute remote code, posing a critical risk to industrial control systems.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6xq6-9j2p-q9cg

## What is CVE-2021-27480?

CVE-2021-27480 is a critical memory corruption vulnerability in Delta Industrial Automation COMMGR, published on 27 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Delta Industrial Automation COMMGR Versions 1.12 and prior are vulnerable to a stack-based buffer overflow, which may allow an attacker to execute remote code.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Deltaww Industrial Automation Commgr.

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

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

## Is CVE-2021-27480 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-27480 is a critical memory corruption vulnerability in Delta Industrial Automation COMMGR, published on 27 Apr 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-27480 in the wild and no public exploit code.

Affected product: Delta Industrial Automation COMMGR. 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-27480/ (Markdown: https://insights.sbomify.com/CVE-2021-27480/index.md)
```

## Sources

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

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