CVE-2024-45238

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) 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.

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.25%
Vendor Advisory github.io
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://nicmx.github.io/FORT-validator/CVE.html vendor advisory

Frequently Asked Questions

What is the severity of CVE-2024-45238?
CVE-2024-45238 has been scored as a high severity vulnerability.
How to fix CVE-2024-45238?
To fix CVE-2024-45238, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-45238 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2024-45238 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.