arm RLDP receiver timeouts and validate FEC before receiver allocation

F-TON-006-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

ton-blockchain/tonReported fixton-blockchain/ton

arm RLDP receiver timeouts and validate FEC before receiver allocation

fixed in public source; rollout not reverified

details

Finding IDs: F-TON-006-001
Status: fixed in public source; rollout not reverified
Reported via: TON contest / security process
Note: PR #2191 merged on 2026-03-09 as d9bc8b9520964817a704949cd6eb50527f595559. The diff arms the receiver alarm in start_up and validates fec_type before receiver creation in RldpIn::process_message_part. These match the reported callsites. F-TON-007-001 describes the same receiver-state defect and is an alternate ID, not a separate counted finding. This source-level mapping does not establish public vendor attribution or a deployed release.

F-TON-006-001: Resource limits. RLDP/FEC work is allocated before the required expiry/resource checks. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TON-006-001

Security area (1seal assessment): Availability. Incomplete or malformed RLDP transfers could retain receiver state without an armed expiry alarm; the matched patch schedules expiry and validates FEC before allocation. Reviewed 23 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.