Route validation crash via null eContent dereference
Published Aug 24, 2024 · Updated Nov 3, 2025
NULL pointer dereference in FORT Validator before 1.6.3 allows remote attackers to crash Route Origin Validation via a malicious RPKI object. The asn1_decode_octet_string path dereferences an absent eContent OCTET STRING in a served ROA or Manifest without a null check. The repository must descend from a trusted Trust Anchor and deliver the object through rsync or RRDP; the resulting crash stops validation and can undermine routing decisions.
Summary
What happened
NULL pointer dereference in FORT Validator before 1.6.3 allows remote attackers to crash Route Origin Validation via a malicious RPKI object. The asn1_decode_octet_string path dereferences an absent eContent OCTET STRING in a served ROA or Manifest without a null check. The repository must descend from a trusted Trust Anchor and deliver the object through rsync or RRDP; the resulting crash stops validation and can undermine routing decisions.
The record
- CVE
- CVE-2024-45239
- Published
- Aug 24, 2024
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo