Vulnerability in net.ripe.rpki:rpki-validator-3 (CVE-2020-16164)
Summary
Vulnerability in net.ripe.rpki:rpki-validator-3 (CVE-2020-16164). Data can be tampered with by attackers. Mitigation: upgrade to 3.2-2020.10.28.23.06 or later.
Original description
The description as published by the source.
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
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-16164 has been found in net.ripe.rpki:rpki-validator-3.
Data can be tampered with by attackers.
What to do: upgrade net.ripe.rpki:rpki-validator-3 to 3.2-2020.10.28.23.06 or later.
If unsure, ask your IT team or search "net.ripe.rpki:rpki-validator-3 CVE-2020-16164" on the vendor's site.
CVE-2020-16164 (net.ripe.rpki:rpki-validator-3) — CWE-20
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.2-2020.10.28.23.06 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in net.ripe.rpki:rpki-validator-3.
Check the vendor advisory for the affected versions of net.ripe.rpki:rpki-validator-3.
Severity: ?. Data can be tampered with by attackers.
Update to 3.2-2020.10.28.23.06.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで net.ripe.rpki:rpki-validator-3 を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade net.ripe.rpki:rpki-validator-3 to 3.2-2020.10.28.23.06ステージング環境で 3.2-2020.10.28.23.06 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- report github.com
- report github.com