# CVE-2021-27417: eCosCentric eCosPro RTOS Integer Overflow or Wraparound

> An integer overflow in the calloc function allows arbitrary memory allocation, leading to heap-based buffer overflows and potential code execution.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 May 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-6gcq-2grw-gh92

## What is CVE-2021-27417?

CVE-2021-27417 is a medium-severity vulnerability in eCosCentric eCosPro RTOS, published on 3 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

eCosCentric eCosPro RTOS Versions 2.0.1 through 4.5.3 are vulnerable to integer wraparound in function calloc (an implementation of malloc). The unverified memory assignment can lead to arbitrary memory allocation, resulting in a heap-based buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Ecoscentric Ecospro.

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

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

## Is CVE-2021-27417 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-27417 is a medium-severity vulnerability in eCosCentric eCosPro RTOS, published on 3 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-27417 in the wild and no public exploit code.

Affected product: eCosCentric eCosPro RTOS. 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-27417/ (Markdown: https://insights.sbomify.com/CVE-2021-27417/index.md)
```

## Sources

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

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