An issue was discovered in Fort before 1.6.3. A malicious RPKI repository that descends from a (trusted) Trust Anchor can serve (via rsync or RRDP) an ROA or a Manifest containing a signedAttrs encoded in non-canonical form. This bypasses Fort's BER decoder, reaching a point in the code that panics when faced with data not encoded in DER. Because Fort is an RPKI Relying Party, a panic can lead to Route Origin Validation unavailability, which can lead to compromised routing.
References
| Link | Resource |
|---|---|
| https://nicmx.github.io/FORT-validator/CVE.html | Third Party Advisory |
| https://lists.debian.org/debian-lts-announce/2025/02/msg00030.html |
Configurations
History
03 Nov 2025, 21:16
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
25 Mar 2025, 19:15
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-295 |
Information
Published : 2024-08-24 23:15
Updated : 2025-11-03 21:16
NVD link : CVE-2024-45234
Mitre link : CVE-2024-45234
CVE.ORG link : CVE-2024-45234
JSON object : View
Products Affected
nicmx
- fort-validator
CWE
