CVE-2020-16163

An issue was discovered in RIPE NCC RPKI Validator 3.x before 3.1-2020.07.06.14.28. RRDP fetches proceed even with a lack of validation of a TLS HTTPS endpoint. This allows remote attackers to bypass intended access restrictions, or to trigger denial of service to traffic directed to co-dependent routing systems. NOTE: third parties assert that the behavior is intentionally permitted by RFC 8182
References
Link Resource
https://github.com/RIPE-NCC/rpki-validator-3/issues/159 Third Party Advisory
Configurations

Configuration 1 (hide)

cpe:2.3:a:ripe:rpki_validator_3:*:*:*:*:*:*:*:*

History

07 Nov 2023, 03:18

Type Values Removed Values Added
Summary ** DISPUTED ** An issue was discovered in RIPE NCC RPKI Validator 3.x before 3.1-2020.07.06.14.28. RRDP fetches proceed even with a lack of validation of a TLS HTTPS endpoint. This allows remote attackers to bypass intended access restrictions, or to trigger denial of service to traffic directed to co-dependent routing systems. NOTE: third parties assert that the behavior is intentionally permitted by RFC 8182. An issue was discovered in RIPE NCC RPKI Validator 3.x before 3.1-2020.07.06.14.28. RRDP fetches proceed even with a lack of validation of a TLS HTTPS endpoint. This allows remote attackers to bypass intended access restrictions, or to trigger denial of service to traffic directed to co-dependent routing systems. NOTE: third parties assert that the behavior is intentionally permitted by RFC 8182

Information

Published : 2020-07-30 16:15

Updated : 2024-08-04 14:15


NVD link : CVE-2020-16163

Mitre link : CVE-2020-16163

CVE.ORG link : CVE-2020-16163


JSON object : View

Products Affected

ripe

  • rpki_validator_3
CWE
CWE-295

Improper Certificate Validation