Blob resolver: properly validate blob size

did:plc:p5yjdr64h7mk5l3kh6oszryk opened this 17d ago 2 comments
did:plc:p5yjdr64h7mk5l3kh6oszryk opened 17d ago

The current remote blob fetch resolver relies entirely on the Content-Length header being truthful, which a malicious PDS could forge to be an inaccurate size which the server would blindly trust. It would be a good idea security-wise to validate the size of the blob as it is fetched by the appview and abort a fetch if it grows too large.

Relevant snippet: https://tangled.org/juprodh.bsky.social/lichen.wiki/blob/main/src/server/routes/blob.ts#L169-172

No activity yet.

cospan · schematic version control on atproto built on AT Protocol