RIPE NCC RPKI Validator up to 3.1-2020.07.06.14.28 Access Restriction certificate validation ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in RIPE NCC RPKI Validator up to 3.1-2020.07.06.14.28. This vulnerability affects unknown code of the component Access Restriction. This manipulation causes certificate validation. This vulnerability is tracked as CVE-2020-16164. The attack is possible to be carried out remotely. No exploit exists. The existence of this vulnerability is still disputed at present.
Details
A vulnerability was found in RIPE NCC RPKI Validator up to 3.1-2020.07.06.14.28. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component Access Restriction. The manipulation with an unknown input leads to a certificate validation vulnerability. The CWE definition for the vulnerability is CWE-295. The product does not validate, or incorrectly validates, a certificate. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
** DISPUTED ** 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.
The weakness was disclosed 07/30/2020. This vulnerability is known as CVE-2020-16164 since 07/30/2020. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1587.003 for this issue.
The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-159216 and VDB-159215 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 3.1-2020.07.06.14.0
- 3.1-2020.07.06.14.1
- 3.1-2020.07.06.14.2
- 3.1-2020.07.06.14.3
- 3.1-2020.07.06.14.4
- 3.1-2020.07.06.14.5
- 3.1-2020.07.06.14.6
- 3.1-2020.07.06.14.7
- 3.1-2020.07.06.14.8
- 3.1-2020.07.06.14.9
- 3.1-2020.07.06.14.10
- 3.1-2020.07.06.14.11
- 3.1-2020.07.06.14.12
- 3.1-2020.07.06.14.13
- 3.1-2020.07.06.14.14
- 3.1-2020.07.06.14.15
- 3.1-2020.07.06.14.16
- 3.1-2020.07.06.14.17
- 3.1-2020.07.06.14.18
- 3.1-2020.07.06.14.19
- 3.1-2020.07.06.14.20
- 3.1-2020.07.06.14.21
- 3.1-2020.07.06.14.22
- 3.1-2020.07.06.14.23
- 3.1-2020.07.06.14.24
- 3.1-2020.07.06.14.25
- 3.1-2020.07.06.14.26
- 3.1-2020.07.06.14.27
- 3.1-2020.07.06.14.28
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.4
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Certificate validationCWE: CWE-295 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/30/2020 🔍07/30/2020 🔍
07/31/2020 🔍
08/04/2024 🔍
Sources
Status: Not definedDisputed: 🔍
CVE: CVE-2020-16164 (🔍)
GCVE (CVE): GCVE-0-2020-16164
GCVE (VulDB): GCVE-100-159217
See also: 🔍
Entry
Created: 07/31/2020 06:36Updated: 08/04/2024 17:17
Changes: 07/31/2020 06:36 (37), 07/31/2020 06:41 (17), 08/04/2024 17:17 (17)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.