Route Origin Validation disablement via unchecked ROA max-length
Published Sep 21, 2021 · Updated Sep 16, 2024
Improper ROA validation in NLnet Labs Routinator 0.9.0 and earlier allows remote attackers to disable Route Origin Validation. Routinator passes an RPKI CA's max-length value through to its RTR payload without checking that it does not exceed the address family's maximum prefix length. A CA able to publish such a ROA can cause RTR clients to reject the entire data set, leaving downstream routers without Route Origin Validation.
Summary
What happened
Improper ROA validation in NLnet Labs Routinator 0.9.0 and earlier allows remote attackers to disable Route Origin Validation. Routinator passes an RPKI CA's max-length value through to its RTR payload without checking that it does not exceed the address family's maximum prefix length. A CA able to publish such a ROA can cause RTR clients to reject the entire data set, leaving downstream routers without Route Origin Validation.
The record
- CVE
- CVE-2021-41531
- Published
- Sep 21, 2021
- Updated
- Sep 16, 2024
- Vendor
- NLnet Labs
- Product
- Routinator
- Classifications
- CWE-20, CWE-1288, T1562
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=0.9.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo