CVE-2024-45239

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 null eContent field. Fort dereferences the 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.

References

Affected packages

Debian:11 / fort-validator

Package

Name: fort-validator
Purl: pkg:deb/debian/fort-validator?arch=source

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

1.5.3-1~deb11u2

Affected versions

1.*

1.5.0-1

1.5.1-1

1.5.2-1

1.5.3-1~deb11u1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / fort-validator

Package

Name: fort-validator
Purl: pkg:deb/debian/fort-validator?arch=source

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Affected versions

1.*

1.5.4-1

1.6.1-1~bpo12+2

1.6.1-1

1.6.2-1

1.6.3-1~bpo12+1

1.6.3-1

1.6.4+20240930-1~bpo12+1

1.6.4+20240930-1

1.6.5-1

1.6.6-1~bpo12+1

1.6.6-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / fort-validator

Package

Name: fort-validator
Purl: pkg:deb/debian/fort-validator?arch=source

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

1.6.3-1

Affected versions

1.*

1.5.4-1

1.6.1-1~bpo12+2

1.6.1-1

1.6.2-1

1.6.3-1~bpo12+1

Ecosystem specific

{
    "urgency": "not yet assigned"
}