Skip to content
Fencer Vulns
high 7.5

CVE-2024-45235 json

An issue was discovered in Fort before 1.6.3.

published 2024-08-24 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-41376

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

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 an Authority Key Identifier extension that lacks the keyIdentifier field. Fort references this pointer without sanitizing it first. Because Fort is an RPKI Relying Party, a crash can lead to Route Origin Validation unavailability, which can lead to compromised routing.

Patch / fix

  • fort_validator_project fort_validator 1.6.3
  • fort-validator Debian 12 1.5.4-1+deb12u1
  • fort-validator Debian 14, Debian 13 1.6.3-1

debian advisories DEBIAN-CVE-2024-45235

  • fort-validator Ubuntu 22.04 LTS 1.5.3-1ubuntu0.1
  • fort-validator Ubuntu Pro 20.04 LTS 1.2.0-1ubuntu0.1~esm1
  • fort-validator Ubuntu Pro 24.04 LTS 1.6.1-1ubuntu0.1~esm2

ubuntu advisories UBUNTU-CVE-2024-45235

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • fort_validator_project fort_validator

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.