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

> A stack buffer overflow in the ASTC encoder library allows attackers to execute arbitrary code or cause a denial of service when using the compression function with specific options.

- **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:** 28 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4jw7-vxxv-4m7h, UBUNTU-CVE-2021-43086

## What is CVE-2021-43086?

CVE-2021-43086 is a critical memory corruption vulnerability in n/a, published on 28 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ARM astcenc 3.2.0 is vulnerable to Buffer Overflow. When the compression function of the astc-encoder project with -cl option was used, a stack-buffer-overflow occurred in function encode_ise() in function compress_symbolic_block_for_partition_2planes() in "/Source/astcenc_compress_symbolic.cpp".

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

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

It affects 1 product.


Products: Arm Adaptive Scalable Texture Compression Encoder.

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

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

## Is CVE-2021-43086 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-44331](https://insights.sbomify.com/CVE-2021-44331/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-43086 is a critical memory corruption vulnerability in n/a, published on 28 Feb 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-43086 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-43086/ (Markdown: https://insights.sbomify.com/CVE-2021-43086/index.md)
```

## Sources

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

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