CVE-2020-6060 json
A stack buffer overflow vulnerability exists in the way MiniSNMPD version 1.4 handles multiple connections.
published 6y ago modified 4mo ago also EUVD-2020-27214
- cvss
- 7.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2020-6060 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.20% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- talosintelligence.com https://talosintelligence.com/vulnerability_reports/TALOS-2019-0977 referenced PoC, tagged "exploit" by a source, unverified
- talosintelligence.com https://www.talosintelligence.com/vulnerability_reports/TALOS-2020-0977 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- n/a Mini-SNMPD
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
talosintelligence.com
/vulnerability_reports/TALOS-2019-0977
exploit, third-party-advisory
-
talosintelligence.com
/vulnerability_reports/TALOS-2020-0977
exploit, third-party-advisory
Sources
- CVE List CVE-2020-6060
- NVD CVE-2020-6060
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.