# CVE-2020-37182: Redir 3.3 - Denial of Service

> Attackers can crash the Redir TCP redirector service by sending oversized input that triggers a stack overflow in the connection handler.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2026
- **Updated:** 12 Feb 2026
- **Also known as:** DEBIAN-CVE-2020-37182, GHSA-64v7-64h5-r58h, UBUNTU-CVE-2020-37182

## What is CVE-2020-37182?

CVE-2020-37182 is a high-severity memory corruption vulnerability in troglobit Redir, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Redir 3.3 contains a stack overflow vulnerability in the doproxyconnect() function that allows attackers to crash the application by sending oversized input. Attackers can exploit the sprintf() buffer without proper length checking to overwrite memory and cause a segmentation fault, resulting in program termination.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2020-37182 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37182 is a high-severity memory corruption vulnerability in troglobit Redir, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37182 exists.

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

## Sources

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

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