CVE-2024-45239: Fort · NULL Pointer Dereference
Source GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 1.6.3 : patch Fort soon.
Data as of 30 Oct 2026, 00:37 UTC
- 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
Weaponized: 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 29 Oct 2026.
What to do
AI-suggested
A fix is available in Fort version 1.6.3. Users should upgrade to version 1.6.3 or later to remediate this vulnerability. No other mitigation or temporary workaround is indicated in the available data.
Description
CVE-2024-45239 is a vulnerability in Fort versions before 1.6.3 where a malicious RPKI repository can cause a crash by serving an ROA or Manifest with a null eContent field. This occurs because Fort dereferences a pointer without proper sanitization. The crash can disrupt Route Origin Validation, potentially compromising routing security.