NLnetLabs Routinator 0.7.1 Release Candidate 2

CPE Details

NLnetLabs Routinator 0.7.1 Release Candidate 2
nlnetlabs
routinator
0.7.1
2020-08-07
17h33 +00:00
2020-08-07
17h33 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:nlnetlabs:routinator:0.7.1:rc2:*:*:*:*:*:*

Informations

Vendor

nlnetlabs

Product

routinator

Version

0.7.1

Update

rc2

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2024-1622 2024-02-26 13h35 +00:00 Due to a mistake in error checking, Routinator will terminate when an incoming RTR connection is reset by the peer too quickly after opening.
7.5
High
CVE-2023-39915 2023-09-13 14h20 +00:00 NLnet Labs' Routinator up to and including version 0.12.1 may crash when trying to parse certain malformed RPKI objects. This is due to insufficient input checking in the bcder library covered by CVE-2023-39914.
7.5
High
CVE-2021-43173 2021-11-09 16h41 +00:00 In NLnet Labs Routinator prior to 0.10.2, a validation run can be delayed significantly by an RRDP repository by not answering but slowly drip-feeding bytes to keep the connection alive. This can be used to effectively stall validation. While Routinator has a configurable time-out value for RRDP connections, this time-out was only applied to individual read or write operations rather than the complete request. Thus, if an RRDP repository sends a little bit of data before that time-out expired, it can continuously extend the time it takes for the request to finish. Since validation will only continue once the update of an RRDP repository has concluded, this delay will cause validation to stall, leading to Routinator continuing to serve the old data set or, if in the initial validation run directly after starting, never serve any data at all.
7.5
High
CVE-2021-43172 2021-11-09 16h41 +00:00 NLnet Labs Routinator prior to 0.10.2 happily processes a chain of RRDP repositories of infinite length causing it to never finish a validation run. In RPKI, a CA can choose the RRDP repository it wishes to publish its data in. By continuously generating a new child CA that only consists of another CA using a different RRDP repository, a malicious CA can create a chain of CAs of de-facto infinite length. Routinator prior to version 0.10.2 did not contain a limit on the length of such a chain and will therefore continue to process this chain forever. As a result, the validation run will never finish, leading to Routinator continuing to serve the old data set or, if in the initial validation run directly after starting, never serve any data at all.
7.5
High
CVE-2021-41531 2021-09-21 13h23 +00:00 NLnet Labs Routinator prior to 0.10.0 produces invalid RTR payload if an RPKI CA uses too large values in the max-length parameter in a ROA. This will lead to RTR clients such as routers to reject the RPKI data set, effectively disabling Route Origin Validation.
7.5
High
CVE-2020-17366 2020-08-05 19h07 +00:00 An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. 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.
7.4
High