NLnet Labs Routinator versions 0.9.0 up to and including 0.10.1, support the gzip transfer encoding when querying RRDP repositories. This encoding can be used by an RRDP repository to cause an out-of-memory crash in these versions of Routinator. RRDP uses XML which allows arbitrary amounts of white space in the encoded data. The gzip scheme compresses such white space extremely well, leading to very small compressed files that become huge when being decompressed for further processing, big enough that Routinator runs out of memory when parsing input data waiting for the next XML element.

The remote Debian 11 host has a package installed that is affected by multiple vulnerabilities as referenced in the dsa-5041 advisory.

  - Any CA issuer in the RPKI can trick OctoRPKI prior to 1.3.0 into emitting an invalid VRP MaxLength     value, causing RTR sessions to terminate. An attacker can use this to disable RPKI Origin Validation in a     victim network (for example AS 13335 - Cloudflare) prior to launching a BGP hijack which during normal     operations would be rejected as RPKI invalid. Additionally, in certain deployments RTR session flapping     in and of itself also could cause BGP routing churn, causing availability issues. (CVE-2021-3761)

  - OctoRPKI does not escape a URI with a filename containing .., this allows a repository to create a file,     (ex. rsync://example.org/repo/../../etc/cron.daily/evil.roa), which would then be written to disk outside     the base cache folder. This could allow for remote code execution on the host machine OctoRPKI is running     on. (CVE-2021-3907)

  - OctoRPKI does not limit the depth of a certificate chain, allowing for a CA to create children in an ad-     hoc fashion, thereby making tree traversal never end. (CVE-2021-3908)

  - OctoRPKI does not limit the length of a connection, allowing for a slowloris DOS attack to take place     which makes OctoRPKI wait forever. Specifically, the repository that OctoRPKI sends HTTP requests to will     keep the connection open for a day before a response is returned, but does keep drip feeding new bytes to     keep the connection alive. (CVE-2021-3909)

  - OctoRPKI crashes when encountering a repository that returns an invalid ROA (just an encoded NUL (\0)     character). (CVE-2021-3910)

  - If the ROA that a repository returns contains too many bits for the IP address then OctoRPKI will crash.
    (CVE-2021-3911)

  - OctoRPKI tries to load the entire contents of a repository in memory, and in the case of a GZIP bomb,     unzip it in memory, making it possible to create a repository that makes OctoRPKI run out of memory (and     thus crash). (CVE-2021-3912)

  - 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. (CVE-2021-43173)

  - NLnet Labs Routinator versions 0.9.0 up to and including 0.10.1, support the gzip transfer encoding when     querying RRDP repositories. This encoding can be used by an RRDP repository to cause an out-of-memory     crash in these versions of Routinator. RRDP uses XML which allows arbitrary amounts of white space in the     encoded data. The gzip scheme compresses such white space extremely well, leading to very small compressed     files that become huge when being decompressed for further processing, big enough that Routinator runs out     of memory when parsing input data waiting for the next XML element. (CVE-2021-43174)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 9c990e67-6e30-11ec-82db-b42e991fc52e advisory.

  - 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. (CVE-2021-43172)

  - 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. (CVE-2021-43173)

  - NLnet Labs Routinator versions 0.9.0 up to and including 0.10.1, support the gzip transfer encoding when     querying RRDP repositories. This encoding can be used by an RRDP repository to cause an out-of-memory     crash in these versions of Routinator. RRDP uses XML which allows arbitrary amounts of white space in the     encoded data. The gzip scheme compresses such white space extremely well, leading to very small compressed     files that become huge when being decompressed for further processing, big enough that Routinator runs out     of memory when parsing input data waiting for the next XML element. (CVE-2021-43174)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
156636	Debian DSA-5041-1 : cfrpki - security update	Nessus	Debian Local Security Checks	critical
156470	FreeBSD : routinator -- multiple vulnerabilities (9c990e67-6e30-11ec-82db-b42e991fc52e)	Nessus	FreeBSD Local Security Checks	high

Detections

Analytics

CVE-2021-43174

high

Tenable Plugins

critical

high