1sealsemantic last-mile verification

Research / Finding

check reflector peer-tag length before subtracting the header size

F-TGDESKTOP-REFLECTOR-001

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

Read the evidence · View in research browse

Recorded evidence

—score not recorded
TelegramMessenger/tgcallsReported fixTelegramMessenger/tgcalls

check reflector peer-tag length before subtracting the header size

partially fixed publicly
details
Finding IDs
F-TGDESKTOP-REFLECTOR-001
Status
partially fixed publicly
Disclosure date
Note
both constructors subtract four only when the raw peer tag is 16 bytes. This closes the matched length-underflow path, not every issue in the broader report. Desktop release inclusion and the full report were not independently retested.

F-TGDESKTOP-REFLECTOR-001: Memory safety. Peer-tag length arithmetic underflows before memory access. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TGDESKTOP-REFLECTOR-001

Security area (1seal assessment): Memory safety. A short peer tag must not underflow the length used for buffer operations. 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.