CVE-2024-56375

An integer underflow was discovered in Fort 1.6.3 and 1.6.4 before 1.6.5. A malicious RPKI repository that descends from a (trusted) Trust Anchor can serve (via rsync or RRDP) a Manifest RPKI object containing an empty fileList. Fort dereferences (and, shortly afterwards, writes to) this array during a shuffle attempt, before the validation that would normally reject it when empty. This out-of-bounds access is caused by an integer underflow that causes the surrounding loop to iterate infinitely. Because the product is permanently stuck attempting to overshuffle an array that doesn't actually exist, a crash is nearly guaranteed.

Published: 2024-12-22 Last update: 2025-04-22 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-56375 is rated Moderate Risk (51/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.39%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-56375

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-02 0.28% 0.39% +0.11%
2 2026-01-30 0.23% 0.28% +0.06%
3 2025-11-21 — 0.23% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-56375

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-56375

OS Trackers for CVE-2024-56375

vendor priority summary link
debian unimportant CVE-2024-56375 unimportant priority: Debian including 1 source packages (fort-validator), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-56375
ubuntu medium CVE-2024-56375 medium priority: Ubuntu including 1 source packages (fort-validator), 6 status rows across 6 suites (focal, jammy, noble, oracular, plucky, upstream): not-affected 4, ignored 1, released 1. https://ubuntu.com/security/CVE-2024-56375

Affected software / configurations for CVE-2024-56375

Vendor Product Version Raw CPE
nicmx fort_validator 1.6.3 cpe:2.3:a:nicmx:fort_validator:1.6.3:*:*:*:*:*:*:*
nicmx fort_validator 1.6.4 cpe:2.3:a:nicmx:fort_validator:1.6.4:*:*:*:*:*:*:*

References for CVE-2024-56375

cvelogic Threat Intelligence