# CVE-2021-43279: Memory corruption in n/a

> An out-of-bounds write in the PRC SDK allows attackers to execute arbitrary code via crafted U3D files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hpj6-g6xh-pqc4

## What is CVE-2021-43279?

CVE-2021-43279 is a high-severity memory corruption vulnerability in n/a, published on 14 Nov 2021. 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

An out-of-bounds write vulnerability exists in the U3D file reading procedure in Open Design Alliance PRC SDK before 2022.10. Crafted data in a U3D file can trigger a write past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Opendesign Oda Prc Software Development Kit.

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

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

## Is CVE-2021-43279 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43277](https://insights.sbomify.com/CVE-2021-43277/): An out-of-bounds read vulnerability exists in the U3D file reading procedure in Open Design Alliance PRC SDK before 2022.10. (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-43279 is a high-severity memory corruption vulnerability in n/a, published on 14 Nov 2021. 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-43279 in the wild and no public exploit code.

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

## Sources

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

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