# CVE-2020-6060: Memory corruption in Mini-SNMPD

> A stack buffer overflow in MiniSNMPD allows remote attackers to cause a denial of service by initiating multiple specially timed SNMP connections.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 4 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h37q-v64p-46fw

## What is CVE-2020-6060?

CVE-2020-6060 is a high-severity memory corruption vulnerability in Mini-SNMPD, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack buffer overflow vulnerability exists in the way MiniSNMPD version 1.4 handles multiple connections. A specially timed sequence of SNMP connections can trigger a stack overflow, resulting in a denial of service. To trigger this vulnerability, an attacker needs to simply initiate multiple connections to the server.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Minisnmpd Project Minisnmpd.

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

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

## Is CVE-2020-6060 being exploited?

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

## Other vulnerabilities in Mini-SNMPD

- [CVE-2020-6058](https://insights.sbomify.com/CVE-2020-6058/): Information disclosure in Mini-SNMPD (high 8.2)
- [CVE-2020-6059](https://insights.sbomify.com/CVE-2020-6059/): Information disclosure in Mini-SNMPD (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6060 is a high-severity memory corruption vulnerability in Mini-SNMPD, published on 4 Feb 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-6060 in the wild and no public exploit code.

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

## Sources

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

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