OctoRPKI lacks contextual out-of-bounds check when validating RPKI ROA maxLength values
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Cloudflare | octorpki | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
Vendor Solution
Upgrade to 1.3.0
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-5041-1 | cfrpki security update |
EUVD |
EUVD-2021-2036 | 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. |
Github GHSA |
GHSA-c8xp-8mf3-62h9 | OctoRPKI lacks contextual out-of-bounds check when validating RPKI ROA maxLength values |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.216% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.