# CVE-2020-27336: Memory corruption in n/a

> Remote attackers can trigger an out-of-bounds read in the Treck IPv6 stack, potentially exposing memory or causing a crash.

- **Severity:** Low 3.7 (`CVSS:3.1/AC:H/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:N`)
- **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 2020
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-53cj-vhvg-mmqf

## What is CVE-2020-27336?

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

### Official description

An issue was discovered in Treck IPv6 before 6.0.1.68. Improper input validation in the IPv6 component when handling a packet sent by an unauthenticated remote attacker could result in an out-of-bounds read of up to three bytes via network access.

Weakness: CWE-20 (Improper Input Validation), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-27336?

It affects 1 product.


Products: Treck Ipv6.

## How do I fix CVE-2020-27336?

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

## Is CVE-2020-27336 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-27337](https://insights.sbomify.com/CVE-2020-27337/): Memory corruption in n/a (high 7.3)
- [CVE-2020-27338](https://insights.sbomify.com/CVE-2020-27338/): Denial of service in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-27336 and fix it if it is affected.

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

## Sources

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

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