1sealsemantic last-mile verification

Research / Finding

enhancement: reject oversized websocket messages

F-TREZOR-BLOCKBOOK-WS-READLIMIT-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
trezor/blockbookReported fixtrezor/blockbook

enhancement: reject oversized websocket messages

merged
details
Finding IDs
F-TREZOR-BLOCKBOOK-WS-READLIMIT-001
Status
merged
Reported via
security contact
Note
public fix commit f8349fcebcdf on 2026-03-11. adds a websocket read limit to stop unbounded message-driven memory growth.

F-TREZOR-BLOCKBOOK-WS-READLIMIT-001: Resource limits. WebSocket reads are not bounded by message size. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TREZOR-BLOCKBOOK-WS-READLIMIT-001

Security area (1seal assessment): Availability. WebSocket reads are not bounded by message size. Reviewed 24 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.