# CVE-2021-38439: GurumDDS Heap-based Buffer Overflow

> A heap-based buffer overflow in GurumDDS allows remote attackers to execute arbitrary code or cause a denial of service.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 5 May 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-g8fv-j97f-qw8r

## What is CVE-2021-38439?

CVE-2021-38439 is a high-severity memory corruption vulnerability in GurumNetworks GurumDDS, published on 5 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of GurumDDS are vulnerable to heap-based buffer overflow, which may cause a denial-of-service condition or remotely execute arbitrary code.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: Gurum Gurumdds.

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

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

## Is CVE-2021-38439 being exploited?

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

## Other vulnerabilities in GurumNetworks GurumDDS

- [CVE-2021-38423](https://insights.sbomify.com/CVE-2021-38423/): GurumDDS Heap-based Incorrect Calculation of Buffer Size (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-38439 is a high-severity memory corruption vulnerability in GurumNetworks GurumDDS, published on 5 May 2022. 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-38439 in the wild and no public exploit code.

Affected product: GurumNetworks GurumDDS. 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-38439/ (Markdown: https://insights.sbomify.com/CVE-2021-38439/index.md)
```

## Sources

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

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