UBUNTU-CVE-2024-56169 (CVE-2024-56169)
Vulnerability from osv_ubuntu – Published: 2024-12-18 05:15 – Updated: 2026-05-20 15:14 – Source websiteA validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "fort-validator",
"binary_version": "1.2.0-1ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "fort-validator",
"purl": "pkg:deb/ubuntu/fort-validator@1.2.0-1ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1.1-2",
"1.1.2-1",
"1.1.3-1",
"1.2.0-1",
"1.2.0-1ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "fort-validator",
"binary_version": "1.5.3-1ubuntu0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "fort-validator",
"purl": "pkg:deb/ubuntu/fort-validator@1.5.3-1ubuntu0.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.5.1-1",
"1.5.2-1",
"1.5.3-1",
"1.5.3-1build1",
"1.5.3-1ubuntu0.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "fort-validator",
"binary_version": "1.6.1-1ubuntu0.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "fort-validator",
"purl": "pkg:deb/ubuntu/fort-validator@1.6.1-1ubuntu0.1~esm2?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.5.4-1",
"1.6.1-1",
"1.6.1-1build2",
"1.6.1-1build3",
"1.6.1-1ubuntu0.1~esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "fort-validator",
"binary_version": "1.6.6-1build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "fort-validator",
"purl": "pkg:deb/ubuntu/fort-validator@1.6.6-1build1?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.6-1",
"1.6.6-1build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "fort-validator",
"binary_version": "1.6.7-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "fort-validator",
"purl": "pkg:deb/ubuntu/fort-validator@1.6.7-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.6-1build1",
"1.6.7-1"
]
}
],
"aliases": [],
"details": "A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.",
"id": "UBUNTU-CVE-2024-56169",
"modified": "2026-05-20T15:14:39Z",
"published": "2024-12-18T05:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2024-56169"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-56169"
},
{
"type": "REPORT",
"url": "https://github.com/NICMx/FORT-validator/issues/82"
},
{
"type": "REPORT",
"url": "https://nicmx.github.io/FORT-validator/CVE.html"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2024-56169"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.