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

> Attackers can cause an information leak via a crafted structure due to a buffer overflow in the ShieldStore enclave component.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-g8g3-v38g-j575

## What is CVE-2021-44283?

CVE-2021-44283 is a high-severity memory corruption vulnerability in n/a, published on 9 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow in the component /Enclave.cpp of Electronics and Telecommunications Research Institute ShieldStore commit 58d455617f99705f0ffd8a27616abdf77bdc1bdc allows attackers to cause an information leak via a crafted structure from an untrusted operating system.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Shieldstore Project Shieldstore.

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

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

## Is CVE-2021-44283 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-44283 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2021-44283 is a high-severity memory corruption vulnerability in n/a, published on 9 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-44283 exists.

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-44283/ (Markdown: https://insights.sbomify.com/CVE-2021-44283/index.md)
```

## Sources

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

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