Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| devel | deferred | 2025-09-29 |
| esm-apps/focal | deferred | 2025-09-29 |
| esm-apps/jammy | deferred | 2025-09-29 |
| esm-apps/noble | deferred | 2025-09-29 |
| focal | ignored | end of standard support, was needs-triage |
| jammy | deferred | 2025-09-29 |
| noble | deferred | 2025-09-29 |
| oracular | ignored | end of life, was needs-triage |
| plucky | ignored | end of life, was deferred [2025-09-29] |
| questing | deferred | 2025-09-29 |
Показывать по
5.3 Medium
CVSS3
Связанные уязвимости
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.
A validation integrity issue was discovered in Fort through 1.6.4 befo ...
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.
5.3 Medium
CVSS3