cve.bz

CVE-2024-45238 nicmx fort validator: NULL Pointer Dereference

7.5 highEPSS 0.3%

High (7.5) in nicmx fort validator. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2024-08-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-45238 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-45238?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-45238?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-45238 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
nicmx:fort_validatorbefore 1.6.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11fort-validator1.5.3-1~deb11u2DLA-4066-1
Debian12fort-validator1.5.4-1+deb12u1DEBIAN-CVE-2024-45238
Debian13, 14fort-validator1.6.3-1DEBIAN-CVE-2024-45238
Ubuntu22.04:LTSfort-validator1.5.3-1ubuntu0.1UBUNTU-CVE-2024-45238 USN-7813-1
UbuntuPro:20.04:LTSfort-validator1.2.0-1ubuntu0.1~esm1UBUNTU-CVE-2024-45238 USN-7813-1
UbuntuPro:24.04:LTSfort-validator1.6.1-1ubuntu0.1~esm2UBUNTU-CVE-2024-45238 USN-7813-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

References

Check your stackJSON