Octorpki CloudFlare Octorpki

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in CloudFlare Octorpki.

By the Year

In 2026 there have been 0 vulnerabilities in CloudFlare Octorpki. Last year, in 2025 Octorpki had 1 security vulnerability published. Right now, Octorpki is on track to have less security vulnerabilities in 2026 than it did last year.

Year Vulnerabilities Average Score
2026 0 0.00
2025 1 5.50
2024 0 0.00
2023 0 0.00
2022 1 7.50
2021 7 7.54

It may take a day or so for new Octorpki vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.

Recent CloudFlare Octorpki Security Vulnerabilities

Root SUID Escalation via rsync in octorpki
CVE-2021-3978 5.5 - Medium - January 29, 2025

When copying files with rsync, octorpki uses the "-a" flag 0, which forces rsync to copy binaries with the suid bit set as root. Since the provided service definition defaults to root ( https://github.com/cloudflare/cfrpki/blob/master/package/octorpki.service ) this could allow for a vector, when combined with another vulnerability that causes octorpki to process a malicious TAL file, for a local privilege escalation.

OctoRPKI RPKI Validation Daemon Denial of Service via Long CA Chains
CVE-2022-3616 7.5 - High - October 28, 2022

Attackers can create long chains of CAs that would lead to OctoRPKI exceeding its max iterations parameter. In consequence it would cause the program to crash, preventing it from finishing the validation and leading to a denial of service. Credits to Donika Mirdita and Haya Shulman - Fraunhofer SIT, ATHENE, who discovered and reported this vulnerability.

Excessive Iteration

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
CVE-2021-3912 6.5 - Medium - November 11, 2021

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).

Allocation of Resources Without Limits or Throttling

If the ROA that a repository returns contains too many bits for the IP address then OctoRPKI will crash.
CVE-2021-3911 6.5 - Medium - November 11, 2021

If the ROA that a repository returns contains too many bits for the IP address then OctoRPKI will crash.

Unchecked Return Value

OctoRPKI crashes when encountering a repository
CVE-2021-3910 7.5 - High - November 11, 2021

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

Improper Input Validation

OctoRPKI does not limit the length of a connection, allowing for a slowloris DOS attack to take place which makes OctoRPKI wait forever
CVE-2021-3909 7.5 - High - November 11, 2021

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.

Resource Exhaustion

OctoRPKI does not limit the depth of a certificate chain
CVE-2021-3908 7.5 - High - November 11, 2021

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.

Infinite Loop

OctoRPKI does not escape a URI with a filename containing "
CVE-2021-3907 9.8 - Critical - November 11, 2021

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.

Directory traversal

Any CA issuer in the RPKI
CVE-2021-3761 7.5 - High - September 09, 2021

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.

Memory Corruption

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for CloudFlare Octorpki or by CloudFlare? Click the Watch button to subscribe.

CloudFlare
Vendor

subscribe