Approved changes feed: RSS · Atom

cpe:2.3:a:fort_validator_project:fort_validator:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorFort Validator Project (984e064f-c8f1-55d4-b8ec-dbe82b5283fd)
ProductFort Validator (e8f84977-0a52-5add-8998-1959a4127ac5)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:deb/debian/fort-validator purl2cpe 2026-06-01 10:12:47.029446
pkg:deb/ubuntu/fort-validator purl2cpe 2026-06-01 10:12:47.029447
pkg:github/nicmx/fort-validator purl2cpe 2026-06-01 10:12:47.029449

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-45238 vulnerable 2026-06-08 06:45:55.626653 Details available
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.
Published: 2024-08-24T00:00:00.000Z
Updated: 2025-11-03T20:39:07.972Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-45237 vulnerable 2026-06-08 06:45:55.625961 Details available
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 Key Usage extension composed of more than two bytes of data. Fort writes this string into a 2-byte buffer without properly sanitizing its length, leading to a buffer overflow.
Published: 2024-08-24T00:00:00.000Z
Updated: 2025-11-03T20:39:06.541Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-45236 vulnerable 2026-06-08 06:45:55.625542 Details available
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 signed object containing an empty signedAttributes field. Fort accesses the set's elements 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.
Published: 2024-08-24T00:00:00.000Z
Updated: 2025-11-03T20:39:05.109Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-45235 vulnerable 2026-06-08 06:45:55.623750 Details available
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.
Published: 2024-08-24T00:00:00.000Z
Updated: 2025-11-03T20:39:03.687Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-43114 vulnerable 2026-06-08 05:36:42.294216 Details available
FORT Validator versions prior to 1.5.2 will crash if an RPKI CA publishes an X.509 EE certificate. This will lead to RTR clients such as BGP routers to lose access to the RPKI VRP data set, effectively disabling Route Origin Validation.
Published: 2021-11-09T00:00:00.000Z
Updated: 2024-10-15T20:27:11.284Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.