YoursFunny 715d6a59b0 fix(photo): sum dimensions in u64 so a huge header cannot wrap ...

plan_photo, target_dims and both pipeline branches added the two u32 dimensions before comparing against PHOTO_MAX_DIMENSION_SUM: u32::MAX + 2 wrapped to 1 and read 'within limits' — the plan said AsIs, and an absurd-sized image would go to Telegram untouched (in debug builds the addition panics instead). The four production sums now widen to u64 first; the test pins the wrap case as TooLarge. PNG caps each dimension at 2^31-1, so a spec-valid file cannot reach this today — the raw header is parsed before any crate validation, which is exactly where a hostile file lands (audit: photo.rs u32 wrap).

2026-09-24 15:25:19 +08:00

..

x-media

refactor(download): fold apply_media_headers into media_request

2026-09-24 04:37:54 +08:00

xmedia-bot

fix(photo): sum dimensions in u64 so a huge header cannot wrap

2026-09-24 15:25:19 +08:00