CVE-2020-16164
HIGHCVE-2020-16164 is a high-severity (CVSS 7.4) CWE-295 vulnerability in net.ripe.rpki:rpki-validator-3. O3 Security confirms whether CVE-2020-16164 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Vulnerability in RPKI manifest validation
Real-World Exposure
net.ripe.rpki:rpki-validator-3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.ripe.rpki:rpki-validator-3 | all versions | 3.2-2020.10.28.23.06 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.ripe.rpki:rpki-validator-3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update net.ripe.rpki:rpki-validator-3 to 3.2-2020.10.28.23.06 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-16164 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2020-16164 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2020-16164. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2020-16164 in your dependencies?
O3 detects CVE-2020-16164 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.