# CVE-2020-37119: Nsauditor 3.2.1.0 - Buffer Overflow (SEH+ASLR bypass (3 bytes overwrite))

> Attackers can execute arbitrary code by triggering a buffer overflow in the DNS Lookup tool via a malicious query.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Feb 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-qpw6-3qr8-fmwg

## What is CVE-2020-37119?

CVE-2020-37119 is a high-severity memory corruption vulnerability in Nsasoft Nsauditor, published on 5 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Nsauditor 3.0.28 and 3.2.1.0 contains a buffer overflow vulnerability in the DNS Lookup tool that allows attackers to execute arbitrary code by overwriting memory. Attackers can craft a malicious DNS query payload to trigger a three-byte overwrite, bypass ASLR, and execute shellcode through a carefully constructed exploit.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Nsasoft Nsauditor.

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

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

## Is CVE-2020-37119 being exploited?

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

## Other vulnerabilities in Nsasoft Nsauditor

- [CVE-2018-25213](https://insights.sbomify.com/CVE-2018-25213/): Nsauditor 3.0.28.0 Local SEH Buffer Overflow (high 8.6)
- [CVE-2019-25597](https://insights.sbomify.com/CVE-2019-25597/): NSauditor 3.1.2.0 Denial of Service via Community Field (medium 6.9)
- [CVE-2020-37130](https://insights.sbomify.com/CVE-2020-37130/): Nsauditor 3.2.0.0 - 'Name' Denial of Service (medium 6.7)
- [CVE-2021-47895](https://insights.sbomify.com/CVE-2021-47895/): Nsauditor 3.2.2.0 - 'Event Description' Denial of Service (medium 6.7)
- [CVE-2021-47815](https://insights.sbomify.com/CVE-2021-47815/): Nsauditor 3.2.3 - Denial of Service (PoC) (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37119 is a high-severity memory corruption vulnerability in Nsasoft Nsauditor, published on 5 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37119 exists.

Affected product: Nsasoft Nsauditor. 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-37119/ (Markdown: https://insights.sbomify.com/CVE-2020-37119/index.md)
```

## Sources

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

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