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

> A stack buffer overflow in Realtek RTL8195AM allows attackers to execute code or cause denial of service via malicious WEP authentication challenges.

- **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:** 22 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rcc4-26h9-5ggq

## What is CVE-2021-39306?

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

### Official description

A stack buffer overflow was discovered on Realtek RTL8195AM device before 2.0.10, it exists in the client code when an attacker sends a big size Authentication challenge text in WEP security.

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

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

It affects 1 product.


Products: Realtek Rtl8195am Firmware.

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

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

## Is CVE-2021-39306 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43573](https://insights.sbomify.com/CVE-2021-43573/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-9395](https://insights.sbomify.com/CVE-2020-9395/): Memory corruption in n/a (high 8.0)
- [CVE-2022-34326](https://insights.sbomify.com/CVE-2022-34326/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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