DEBIAN-CVE-2024-45239

See a problem?
Please try reporting it to the source first.
Source
https://security-tracker.debian.org/tracker/DEBIAN-CVE-2024-45239
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2024-45239.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2024-45239
Upstream
Published
2024-08-24T23:15:04Z
Modified
2025-09-19T07:34:04.069855Z
Summary
[none]
Details

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
Fixed
1.5.4-1+deb12u1

Affected versions

1.*

1.5.4-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

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:14 / 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

Ecosystem specific 

{
    "urgency": "not yet assigned"
}