CVE-2020-36562 json
Uncontrolled Resource Consumption in github.com/shiyanhui/dht
published 5y ago modified 4mo ago also GHSA-p6fg-723f-hgpw , GO-2020-0040 , EUVD-2022-7699
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
Due to unchecked type assertions, maliciously crafted messages can cause panics, which may be used as a denial of service vector.
Is CVE-2020-36562 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/shiyanhui/dht/issues/57 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/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 |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/shiyanhui/dht | <=0.0.0-20201219151056-5a20f3199263 all versions |
no fix listed |
Affected products
- github.com/shiyanhui/dht github.com/shiyanhui/dht
Classification
References
-
github.com
/shiyanhui/dht/issues/57
web, exploit, issue-tracking, third-party-advisory
-
pkg.go.dev
/vuln/GO-2020-0040
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-36562
advisory
-
github.com
/shiyanhui/dht
package
Sources
- CVE List CVE-2020-36562
- GitHub Advisory GHSA-p6fg-723f-hgpw
- NVD CVE-2020-36562
- OSV GO-2020-0040
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.