Details
Impact
This issue is a sensitive information disclosure that becomes an authentication bypass against .goshs-protected content. Any unauthenticated observer who can access the public collaborator websocket can steal folder-level basic-auth credentials from a victim request and immediately reuse them to read, upload, overwrite, or delete files inside the protected subtree. Deployments that rely on public goshs access with selective .goshs-protected subfolders are directly exposed.
Remediation
Suggested fixes:
- Never store or broadcast sensitive headers such as
Authorization,Cookie, orProxy-Authorizationin collaborator events. - Move collaborator logging until after access-control checks, and log only minimal metadata instead of raw headers and bodies.
- Protect the collaborator websocket and panel with the same or stronger authentication boundary as the resources being observed.