Threat database

FORT Validator versions up to 1.6.7 have an origin validation error in their RRDP processing that allows a delegated CA under the same Trust Anchor Locator to reference another CA's RRDP URLs. This can cause FORT Validator to delete the victim CA's local snapshot and silently remove validated route-origin data, potentially enabling route hijacking or loss of reachability. Version 1.6.8 includes a patch that rejects cross-origin RRDP snapshot and delta URLs. As a workaround, administrators can disable HTTP/RRDP while keeping rsync enabled, though this may cause data unavailability or staleness where rsync is unsupported.

An integer underflow was discovered in Fort 1.6.3 and 1.6.4 before 1.6.5. A malicious RPKI repository that descends from a (trusted) Trust Anchor can serve (via rsync or RRDP) a Manifest RPKI object containing an empty fileList. Fort dereferences (and, shortly afterwards, writes to) this array during a shuffle attempt, before the validation that would normally reject it when empty. This out-of-bounds access is caused by an integer underflow that causes the surrounding loop to iterate infinitely. Because the product is permanently stuck attempting to overshuffle an array that doesn't actually exist, a crash is nearly guaranteed.