Skip to content

OctoRPKI crashes when max iterations is reached

Moderate severity GitHub Reviewed Published Oct 28, 2022 in cloudflare/cfrpki • Updated Oct 2, 2023

Package

gomod github.com/cloudflare/cfrpki (Go)

Affected versions

<= 1.4.3

Patched versions

1.4.4

Description

Impact

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.

Specific Go Packages Affected

github.com/cloudflare/cfrpki/cmd/octorpki

Patches

This issue is fixed in v1.4.4

Workarounds

None.

References

@mskowroncf mskowroncf published to cloudflare/cfrpki Oct 28, 2022
Published by the National Vulnerability Database Oct 28, 2022
Published to the GitHub Advisory Database Oct 31, 2022
Reviewed Oct 31, 2022
Last updated Oct 2, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:H

EPSS score

0.081%
(37th percentile)

Weaknesses

CVE ID

CVE-2022-3616

GHSA ID

GHSA-pmw9-567p-68pc

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.