CVE-2024-45234: Fort · Improper Certificate Validation
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 1.6.3 : patch Fort soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- Fort before 1.6.3
- Patch
- Available – fixed in 1.6.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
European organizations using Fort should immediately upgrade to version 1.6.3 or later, where this vulnerability is fixed. In addition, network operators should implement strict validation of RPKI data encoding to detect and reject non-canonical BER encodings before they reach Fort. Deploying monitoring tools that alert on unexpected RPKI repository behavior or Fort process crashes can provide early warning of exploitation attempts. Organizations should also consider deploying redundant RPKI validators to maintain validation availability in case of a crash. Network operators can restrict access to RPKI repositories to trusted sources and monitor synchronization protocols (rsync, RRDP) for anomalies. Coordination with upstream providers and participation in information sharing groups focused on routing security can enhance situational awareness. Finally, organizations should review their incident response plans to include scenarios involving RPKI validation failures and routing hijacks.
Description
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.