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) a resource certificate containing a bit string that doesnt properly decode into a Subject Public Key. OpenSSL does not report this problem during parsing, and when compiled with OpenSSL libcrypto versions below 3, Fort recklessly dereferences the pointer. Because Fort is an RPKI Relying Party, a crash can lead to Route Origin Validation unavailability, which can lead to compromised routing.
Weakness
The product dereferences a pointer that it expects to be valid but is NULL.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Fort_validator | Nicmx | * | 1.6.3 (excluding) |
| Fort-validator | Ubuntu | esm-apps/focal | * |
| Fort-validator | Ubuntu | esm-apps/jammy | * |
| Fort-validator | Ubuntu | esm-apps/noble | * |
| Fort-validator | Ubuntu | focal | * |
| Fort-validator | Ubuntu | jammy | * |
| Fort-validator | Ubuntu | noble | * |
| Fort-validator | Ubuntu | oracular | * |
| Fort-validator | Ubuntu | upstream | * |