First published: Sat Aug 24 2024(Updated: )
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 doesn't 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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Fortinet FortiGate | <1.6.3 | |
OpenSSL | <3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-45238 has been classified as a medium severity vulnerability due to its potential to compromise resource certificate validation.
To fix CVE-2024-45238, upgrade Fort to version 1.6.3 or later and ensure OpenSSL is updated to version 3 or higher.
CVE-2024-45238 affects all versions of Fort prior to 1.6.3.
CVE-2024-45238 impacts OpenSSL versions prior to 3.
Exploitation of CVE-2024-45238 could allow an attacker to serve a malicious resource certificate, potentially leading to unauthorized access to systems relying on the affected software.