Skip to content
Fencer Intel
high 7.4

CVE-2020-16164 json

Vulnerability in RPKI manifest validation

published 6y ago modified 4mo ago also GHSA-q76j-58cx-wp5v , EUVD-2020-8130

cvss
7.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

An issue was discovered in RIPE NCC RPKI Validator 3.x through 3.1-2020.07.06.14.28. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate Revocation List files from the RPKI relying party's view. NOTE: some third parties may regard this as a preferred behavior, not a vulnerability

Patch / fix

  • maven net.ripe.rpki:rpki-validator-3 3.2-2020.10.28.23.06

Is CVE-2020-16164 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 Fencer

Exploit prediction

0.91% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:N/I:P/A:P

Affected packages

ecosystem package affected fixed in
maven net.ripe.rpki:rpki-validator-3
<3.2-2020.10.28.23.06
3.2-2020.10.28.23.06

Classification

Weakness
  • CWE-295 Improper Certificate Validation
  • CWE-20 Improper Input Validation

References

Sources

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.