CVE-2024-45234: An issue was discovered in Fort before 1.6.3

Q: How do I fix CVE-2024-45234?

fort-validator: upgrade to 1.6.3. Exact commands for each OS are on this page.

Q: Is CVE-2024-45234 being exploited?

CVE-2024-45234 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-45234 affect?

CVE-2024-45234 affects fort-validator. Severity is high (CVSS 7.5). 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) an ROA or a Manifest containing a signedAttrs encoded in non-canonical form. This bypasses F

Q: How urgent is CVE-2024-45234?

Priority 41/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2024-45234 is a high-severity flaw (CVSS 7.5) affecting fort-validator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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) an ROA or a Manifest containing a signedAttrs encoded in non-canonical form. This bypasses Fort's BER decoder, reaching a point in the code that panics when faced with data not encoded in DER. Because Fort is an RPKI Relying Party, a panic can lead to Route Origin Validation unavailability, which can

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 61%)
CISA exploited list	No
Weakness	CWE-295
Published	2024-08-24
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: nicmx

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-08-24 23:15 UTCPublished CVE record published
2026-06-17 07:53 UTCUpdated Record last modified

nicmx fort-validator UPGRADE

Affected: < 1.6.3

Fixed in: 1.6.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy fort-validator || rpm -q fort-validator || fort-validator --version

2. UPGRADE to 1.6.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade fort-validator

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade fort-validator

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-45234?

fort-validator: upgrade to 1.6.3. Exact commands for each OS are on this page.

Is CVE-2024-45234 being exploited?

CVE-2024-45234 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-45234 affect?

CVE-2024-45234 affects fort-validator. Severity is high (CVSS 7.5). 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) an ROA or a Manifest containing a signedAttrs encoded in non-canonical form. This bypasses F

How urgent is CVE-2024-45234?

Priority 41/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-56170 MEDIUM 5.3 UPGRADE A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0
CVE-2024-45239 HIGH 7.5 UPGRADE An issue was discovered in Fort before 1.6.3
CVE-2024-45237 CRITICAL 9.8 UPGRADE An issue was discovered in Fort before 1.6.3
CVE-2024-45236 HIGH 7.5 UPGRADE An issue was discovered in Fort before 1.6.3

References

← Back to latest CVEs