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

> An out-of-bounds read in Bftpd causes the daemon to crash at startup, resulting in a denial of service.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 10 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-568h-8j2j-wm8w

## What is CVE-2020-6162?

CVE-2020-6162 is a critical memory corruption vulnerability in n/a, published on 10 Jan 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 Bftpd 5.3. Under certain circumstances, an out-of-bounds read is triggered due to an uninitialized value. The daemon crashes at startup in the hidegroups_init function in dirlist.c.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Bftpd Project Bftpd.

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

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

## Is CVE-2020-6162 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-6835](https://insights.sbomify.com/CVE-2020-6835/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-16892](https://insights.sbomify.com/CVE-2017-16892/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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