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

> Remote attackers can execute arbitrary code, cause denial of service, or leak information via a malicious DNS response packet in the NicheStack TCP/IP stack.

- **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:** 18 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p4cr-qpf4-f593

## What is CVE-2020-25928?

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

### Official description

The DNS feature in InterNiche NicheStack TCP/IP 4.0.1 is affected by: Buffer Overflow. The impact is: execute arbitrary code (remote). The component is: DNS response processing functions: dns_upcall(), getoffset(), dnc_set_answer(). The attack vector is: a specific DNS response packet. The code does not check the "response data length" field of individual DNS answers, which may cause out-of-bounds read/write operations, leading to Information leak, Denial-or-Service, or Remote Code Execution, depending on the context.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Hcc-Embedded Nichestack Tcp\/Ip.

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

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

## Is CVE-2020-25928 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-25926](https://insights.sbomify.com/CVE-2020-25926/): Other in n/a (high 7.5)
- [CVE-2020-25927](https://insights.sbomify.com/CVE-2020-25927/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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