Server-side request forgery (SSRF) In github.com/getarcaneapp/arcane/backend

Description

Arcane has Unauthenticated SSRF with Conditional Response Reflection in Template Fetch Endpoint

Summary

The /api/templates/fetch endpoint accepts a caller-supplied url parameter and performs a server-side HTTP GET request to that URL without authentication and without URL scheme or host validation. The server's response is returned directly to the caller. type. This constitutes an unauthenticated SSRF vulnerability affecting any publicly reachable Arcane instance.

Details

    No allowlist or denylist of destination hosts/CIDRs

    No requirement for the caller to be authenticated

Response handling produces four distinct outcomes observable by the caller:

    Valid JSON targets return a fully reflected response body if the returned fields fit the expected internal struct

    Non-JSON HTTP 200 responses produce an error leaking the first byte of the response ("Invalid JSON response: invalid character '<'...")

    Non-200 responses leak the HTTP status code

    TCP-level failures distinguish between closed ports ("connection refused") and filtered ones ("i/o timeout")

PoC

Send an unauthenticated GET request to /api/templates/fetch, passing the target URL as the url query parameter.

image

Impact

    Unauthenticated port scanning of internal networks

    Access to internal HTTP services not exposed to the public internet (service discovery endpoints, internal dashboards, Kubernetes API)

Mitigation

Update Impact

Minimal update. May introduce new vulnerabilities or breaking changes.

Ecosystem
Package
Affected version
Patched versions