Maurice 97ebe23d3b fix(server): bound every outbound fetch ...

The rule is a timeout, a size cap and boundary validation on anything that
leaves the process, and several call sites had only the timeout. A link
preview, a maps URL resolve, a wiki fallback and a holiday lookup all read
the whole body into memory, so a caller who picks the URL picks how much
memory the server spends - a few concurrent multi-hundred-megabyte responses
is the whole heap.

Two of them also fetched more than their name suggests. resolve-url fell
through to a full page GET for any host once it found no coordinates, which
makes the server a general-purpose outbound proxy wearing its own IP. The
weather URLs took lat/lng straight from the caller into the query string.

readCapped/exceedsDeclaredLength collect the pattern transit.service.ts and
the plugin installer had each grown separately, so there is one of it now.
Callers that only scan the head of a document (og: tags, a coordinate regex)
keep the truncated bytes and find fewer fields; callers that must have the
whole thing reject it.

2026-08-23 11:59:12 +02:00

..

cappedFetch.test.ts

fix(server): bound every outbound fetch

2026-08-23 11:59:12 +02:00

ipv6.test.ts

v3.4.0 (#1540)

2026-07-18 22:13:52 +02:00

ssrfGuard.test.ts

v3.4.0 (#1540)

2026-07-18 22:13:52 +02:00