VulnWatch by ve1ve2
medium 4.3

GHSA-86ch-2247-gr56: Unauthenticated Host-header injection and RSS cache poisoning

Source:
Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)
Published:
Fetched:
Updated:
Affects:
louislam uptime-kuma

https://github.com/louislam/uptime-kuma/security/advisories/GHSA-86ch-2247-gr56 ↗

repo-advisoryothersecurityrepo:louislam/uptime-kuma

Unauthenticated Host-header injection and RSS cache poisoning ### Summary GET /status/:slug/rss builds the RSS from the request's Host header (StatusPage.buildRSSUrl in server/model/status_page.js). The response is cached for 5 minutes by apicache, whose key is only req.originalUrl; it does not include Host and does not send Vary: Host. An unauthenticated attacker can request the public RSS URL with Host: attacker.example, poisoning the shared cache. For the next 5 minutes, every client that fetches the same RSS URL receives a channel link pointing to the attacker's domain. The window can be renewed by re-priming. This is link/content spoofing (phishing, brand impersonation), not XSS; the feed library XML-escapes the value. ### Details Affected code: - server/model/status_page.js, buildRSSUrl(): uses request.get("host") to build the link. - server/routers/status-page-router.js: router.get("/status/:slug/rss", cache("5 minutes"), ...) with no Vary: Host. - server/modules/apicache/apicache.js: cache key = req.originalUrl; Host is not included. Preconditions: - Default installation; trustProxy is not required (works with it off). - A public status page slug exists (it is a public URL by design). - Victim fetches /status//rss within the 5-minute TTL. Affected versions: 2.5.8 (current "2" image). The same code path is present on master. If trustProxy is enabled, X-Forwarded-Host is also spoofable. No XSS/RCE: the feed library XML-escapes the value. Only the RSS output is affected; HTML SSR and /api/status-page/* bodies are not Host-dependent (tested). ### Proof of concept 1) Prime the cache with an attacker Host: GET /status/hunt-status/rss HTTP/1.1 Host: canonical-evil.example Response contains: http://canonical-evil.example/status/hunt-status curl -sS -H 'Host: canonical-evil.example' \ http://127.0.0.1:3001/status/hunt-status/rss 2) Fetch the same URL with the normal Host: GET /status/hunt-status/rss HTTP/1.1 Host: 127.0.0.1:3001 The body still contains http://canonical-evil.example/status/hunt-status, served from the shared cache. 3) Independent network namespace (also confirms it is not a local-cookie effect): docker run --rm --network host alpine:latest \ sh -c "wget -q -O - 'http://127.0.0.1:3001/status/hunt-status/rss'" Same evil link. Confirmed in two independent prime→victim rounds, including after the canonical URL's TTL expired; an unprimed control returned the normal URL. Replace "hunt-status" with any public status page slug. Raw HTTP/headers/logs are in the attached zip. ### Impact - Pre-auth attacker redirects the RSS channel link (and any item links derived from it) to an attacker domain; feed-reader "open site" clicks go to the attacker (phishing / brand impersonation). - Poisoning lasts 5 minutes and can be renewed indefinitely; all clients share the in-process cache. - No XSS, RCE, or data disclosure. Only the RSS out Affected packages: other:uptime-kuma Patched: uptime-kuma 2.5.9

Linked vulnerabilities (1)

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Unauthenticated Host-header injection and RSS cache poisoning

Also reported by (1)