Fedify affected by resource exhaustion caused by unbounded redirect following during remote key/document resolution
@fedify fedify · @fedify vocab-runtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @fedify/fedify npm |
|
|
@fedify fedify · @fedify vocab-runtime
| Product | Affected | Fixed in |
|---|---|---|
| @fedify/fedify npm |
|
|
| @fedify/vocab-runtime npm |
|
|
Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Prior to 1.9.6, 1.10.5, 2.0.8, and 2.1.1, @fedify/fedify follows HTTP redirects recursively in its remote document loader and authenticated document loader without enforcing a maximum redirect count or visited-URL loop detection. An attacker who controls a remote ActivityPub key or actor URL can force a server using Fedify to make repeated outbound requests from a single inbound request, leading to resource consumption and denial of service. This vulnerability is fixed in 1.9.6, 1.10.5, 2.0.8, and 2.1.1.
From the CVE record · GitHub_M
Fedify’s remote and authenticated document loaders follow HTTP redirects without a redirect limit or loop detection. An attacker controlling a remote ActivityPub key or actor URL can cause repeated outbound requests from a single inbound request, consuming server resources and potentially causing denial of service.
Check servers using @fedify/fedify versions below 1.9.6, 1.10.0–1.10.4, 2.0.0–2.0.7, or 2.1.0, and installations of @fedify/vocab-runtime below 2.0.8 or at 2.1.0.