CVE-2017-20180 json
Zerocoin libzerocoin Proof CoinSpend.cpp CoinSpend data authenticity
published 2023-03-06 3 y ago modified 2026-06-17 4 mo ago also EUVD-2017-11175
- cvss
- 4.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
A vulnerability classified as critical has been found in Zerocoin libzerocoin. Affected is the function CoinSpend::CoinSpend of the file CoinSpend.cpp of the component Proof Handler. The manipulation leads to insufficient verification of data authenticity. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The patch is identified as ce103a09ec079d0a0ed95475992348bed6e860de. It is recommended to apply a patch to fix this issue. VDB-222318 is the identifier assigned to this vulnerability.
Patch / fix
- zerocoin libzerocoin 2017-11-15
- github.com/Zerocoin/libzerocoin@ce103a0 commit
- github.com/Zerocoin/libzerocoin#16 pull request
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.6 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
| CNA | 3.0 | 4.6 | CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
| CNA | 2.0 | 4.1 | AV:A/AC:L/Au:S/C:N/I:P/A:P |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Zerocoin libzerocoin
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
github.com
/Zerocoin/libzerocoin/pull/16
issue-tracking, patch
-
github.com
/Zerocoin/libzerocoin/commit/ce103a09ec079d0a0ed95475992348bed6e860de
patch
-
vuldb.com
/?id.222318
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.222318
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2017-20180
- NVD CVE-2017-20180
Fencer Vulns 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.